Software Vault: The Diamond Collection

home *** CD-ROM | disk | FTP | other *** search

/ Software Vault: The Diamond Collection / The Diamond Collection (Software Vault)(Digital Impact).ISO / cdr29 / warpinst.zip / WARPINST.DOC < prev next >

Wrap

Text File | 1995-01-24 | 161KB | 3,912 lines

Copyright information The contents of this document are Copyright IBM Corp. 1981-1995. All rights reserved. Information current as of January 23, 1995 TXT versions by Irv Spalten INF file by Chris Novak These are solutions to problems encountered in OS/2 Warp. TITLE: 941027 INSTALLATION OF WARP HANG ON DISK #1 WHEN INSTALL ON GATEWAY COMPUTERS. DESCRIPTION OF SYMPTOMS: Hang on DISK #1 when installing WARP on Gateway machines. RESOLUTION: If you are having this problem, please check the level of BIOS on your system. If you have a Gateway 1.00.03.AF1 BIOS, then you need to update your BIOS (see the README). A fix is available from Gateway. TITLE: 941028 Problem installing "Internet Connection for OS/2" portion of the Warp BonusPack from CDROM on Mitsumi CDROM drives. DESCRIPTION OF SYMPTOMS: User experiences XDFCOPY error message XDF3507 when trying to make the diskettes for the Internet portion of the Warp BonusPack. The error occurs ONLY on the INETCON1,2,3 & 4.IMG files. The rest of the BonusPack installs fine from the CDROM. If the user tries to install directly from the CDROM using the BonusPack installation menu instead of making the diskettes using XDFCOPY, he'll get UNZIP errors as shown below (in this example G: is the CDROM drive letter): g:\internet\iak1.zip" did not unzip correctly (rc=-51). Do you wish to continue the installation? If the user chooses to continue installation he'll get the same error on iak2,3 & 4.zip files as well. Finally the BonusPack installation program will error out by reporting similar to the following: The exit program for "IBM Internet Connection for OS/2" gave a bad return code of 65535. Continue with the installation? If the user selects OK then the system will abort the install. SUMMARY OF RESOLUTION: The user has the following options: 1.) Try and run the XDFCOPY on another machine with a different CDROM drive. The resulting diskettes can be used to install on the machine that is failing. 2.) Have the customer attempt to copy the .IMG files from the CDROM to a temporary subdirectory in his disk drive and run XDFCOPY from the .IMG files on the disk drive. 3.) Have the user check the BonusPack CDROM for any dirt or scratches. CDROMs can suffer from the same read problems as audio CDs can. Also inspect the CD CADDY it is installed in or the CDROM drive drawer area for any dust or dirt. 4.) If none of the above suggestions work, recommend that the user obtain a replacement BonusPack CDROM DETAILS OF RESOLUTION: This problem has been observed to occur on Mitsumi CDROM drives (FX-001D and FX-100D). It may occur on others too. It appears to be a CDROM drive read problem. It is possible that the drive electronics and/or mechanics are not aligned (i.e. out of tolerance or spec.) such that a read error occurs on the BonusPack CDROM. The customers that experienced this problem, were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error. The failure was only seen on the "Internet Connection for OS/2" component of the Warp BonusPack CDROM. TITLE: 941114 Configuring the NEC 260 IDE cdrom under OS2 Warp. DESCRIPTION OF SYMPTOMS: A NEC 260 IDE cdrom is not being recognized by OS2 Warp. SUMMARY OF RESOLUTION: Make sure the proper drivers are loading in config.sys and that the necessary files are located in the proper directories. DETAILS OF RESOLUTION: If you have already installed OS2 Warp, and are trying to get the cdrom recognized, follow these instructions: 1. Go to the OS2 Selective Install utility. From the list of cdrom's, select the NEC 260. Click OK. At the System Configuration window, click OK again. At the Setup and Installation window, select the Install button. 2. Insert the OS2 diskette when prompted. 3. Edit the OS2 config.sys in the root directory of the hard drive. Find the line: BASEDEV=IBM1S506.ADD Add switches to this line so that it reads: BASEDEV=IBM1S506.ADD /A:x /U:y /ATAPI The /A switch refers to the adapter number that the cdrom is attached to. The /U option references the unit or device number on a particular adapter. The /ATAPI parameter enables ATA Packet Interface protocol for the NEC 260. If the cdrom is attached to the second IDE port or adapter in a system and is the only device on the adapter, you would enter BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI in the config.sys. If the cdrom is configured as a slave, or sec device, you would specify /U:1. The config.sys should also conta the statements: BASEDEV=IBMIDECD.FLT DEVICE=C:\OS2\BOOT\OS2CDROM.DMD IFS=C:\OS2\BOOT\CDFS.IFS These should have been added by the Selective Install program. If you are trying to install Warp from the NEC 260 cdrom, simply configure the BASEDEV=IBM1S506.ADD line per above. If you find that OS2 still does not recognize the cdrom, make sure that the /A and /U parameters are specified TITLE: 941027 4030VL, Promise VLB Diskcaching Card IDE controller failed installing Warp. DESCRIPTION OF SYMPTOMS: Even with cache disabled, the motherboard bios for disk I/O and all ide drives above 0 and 1 disconnected a complete failure with the repeated message that drive C is not available and so forth all the way thru D and the logical drive partitions on both physical drives. Note: the above is an example if the user has 2 physical drives connected to this Promise card. RESOLUTION: Get a newer driver available from the Promise BBS. The file is PTI1S506.ADD. When using this, the IBM1S506.ADD must be remmed out first. The older driver for DV4030VLIDE will not work. TITLE: 941026 THE SWAPPER FILE IN WARP. DESCRIPTION OF SYMPTOMS: The swapper file is larger in WARP than in previous releases of OS2. SUMMARY OF RESOLUTION: This is normal. DETAILS OF RESOLUTION: This is normal. The most significant change that has been made is how system DLL's get loaded and what is now valid data for swapping. System DLL's include: DISPLAY SOM PMMERGE PMWP DOSCALL1 PMATM PMMLE IBMDEV32 PMCTLS PMSPL IBMVGA32 PMGPI PMVIOP In the previous versions of OS/2, dll code was never copied to the swapper file. In WARP, code for system dll's can be written to the swapper file and, in adition, during boot, PMMERGE, DOSCALL1, PMGPI, PMWP and PMVIOP will be swapped out. This means that there will be an overall increase in swapper size. This was done to increase overall system perfomance. TITLE: 941115 Warp TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT DESCRIPTION OF SYMPTOMS: When installing TCPIP Version 2.0 and The Internet Connection Kit you will receive an error message that the products are not supported when running TOGETHER. It will install, but there are several problems and certain features will not work. SUMMARY OF RESOLUTION: Running TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT together under WARP is NOT supported. DETAILS OF RESOLUTION: Running TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT together under WARP is NOT supported. TITLE: 941121 TRAP0003 DISK #1 IBM1FLPY.ADD WARP OS/2. CS:EIP=0538:00001a21 CSLIM=000027d7. DESCRIPTION OF SYMPTOMS: Installing WARP disk #1 failed with TRAP0003 on the following values: CS:EIP=0538:00001a21 CSLIM=000027d7. SUMMARY OF RESOLUTION: On the system setup bios, check the SETUP for the floppy drive setup. Make sure that the floppy drive is setup correctly. Example: If user has 1.44mb (3 1/2") drive, make sure the setup reflects 1.44mb setup instead of 1.2mb (5 1/4"). TITLE: 941115 CHANGES MADE BY WARP TO WINDOWS FILES DESCRIPTION OF SYMPTOMS: Changes to several Windows files occur during installation of OS/2 3.0 Warp SUMMARY OF RESOLUTION: The Following Windows files are Modified during WARP installation: WIN.INI SYSTEM.INI WIN.COM CONTROL.INI PROGMAN.INI SETUP.INF CONTROL.INF DETAILS OF RESOLUTION: Changes to the following files are as follows: WIN.INI .Windows. if no printer is defined in WINDOWS, Warp will insert GENERIC / TEXT ONLY in the DEVICE= statement. .Desktop. Adds ICON SPACING=100 note:this statement may or may not appear in this section. If it does not, Warp will insert it .Ports. Adds .OS2 ports .Pscript. This section is created and the following statements are added: EXTERNAL PRINTERS=6 PRINTER1=40291760 PRINTER2=40291730 PRINTER3=40293930 PRINTER4=40293960 PRINTER5=IBM17521 PRINTER6=IBM39521 .Device. This section is created and the following statement is inserted: GENERIC/TEXT ONLY TTY, LPT1: .Printer Ports. This section is created and the following statement is inserted: GENERIC / TEXT ONLY=TTY,LPT1:,15,45 SYSTEM.INI .Boot. LANGUAGE.DLL= is modified to =LANGENG.DLL ( to ensure english) SYSTEM.DRV= is modified to =ATMSYS.DRV MAVDMApps= is added OS2MOUSE.DRV=MOUSE.DRV is added ATM.SYSTEM.DRV=SYSTEM.DRV is added USEOS2SHIELD=1 is added OS2SHIELD=WINSHELD.EXE .Keyboard. KEYBOARD.DLL= is modofied to =KBDUS.DLL .386Enh. MAY change the path in the PAGING FILE= statement Changes the MAXPAGINGFILESIZE= statement .Timer.drv. This section is created and the following statements are inserted: Max386Res=10 Max286Res=10 CONTROL.INI .Installed. This section is created and the following statements are inserted: 3.1=YES HPPCL5A.DRV=yes FINSTALL.DLL=YES FINSTALL.HLP=YES HPPCL5A.HLP=YES HPPCL50P.HLP=YES note: the reference to the HP universal print drivers are due to an HP LaserJet being selected during install. .Function. This section is created and the following statement is inserted: SETTINGS=COLORS, FONTS, PORTS, MOUSE, DESTOP, PRINTERS INTERNATIONAL, SOUND, NETWORK PROGMAN.INI .Settings. display.drv=<installed resolution> is inserted SETUP.INF .oemdisks. A =. ,"IBM OS/2 Printer Driver Diskette 1","PMDD 1" B =. ,"IBM OS/2 Printer Driver Diskette 2","PMDD 2" C =. ,"IBM OS/2 Printer Driver Diskette 3","PMDD 3" TITLE: 941121 INSTALLING WARP, GETTING SYS0045 ON WINDOWS DISK #1 DESCRIPTION OF SYMPTOMS: Installing OS/ WARP passed the first phase and onto the second phase of the installation, when asks to insert the WINDOWS DISK #1, will received a " SYS0045 sector can't be found ... " If going into OS/2 and DIR on the WINDOWS DISKS, it is ok, but if trying to copy, xcopy any files from the WINDOWS DISKS to the hardfile, result the same error SYS0045 message. SUMMARY OF RESOLUTION: User has changed the floppy drives around and did not update the CMOS to reflects the changes. DETAILS OF RESOLUTION: User must go into the system CMOS and make sure the floppy drives are setup correctly. Example: If changed the 1.44mb drive from B: to A:, and the 1.2mb drive from A: to B:, on the Setup on the CMOS should reflect that 1.44mb as an A: drive and 1.2mb as an B: drive. TITLE: 941121 WIN-OS2 SESSIONS FAIL TO LAUNCH. BOOTLOG.TXT HAS AS IT,S LAST STATEMENT, "LOADSTART=MOUSE.DRV" DESCRIPTION OF SYMPTOMS: WIN-OS/2 fails to launch if there is no mouse type specified in MOUSE.INI SUMMARY OF RESOLUTION: Ensure the MOUSE.INI file has a type specified DETAILS OF RESOLUTION: When starting any WIN-OS/2 session (FS or Seamless), the session will terminate before it starts. If initiated from an ICON, it will hatch then unhatch. If initiated from a command line, "Loading Please Wait..." will appear, then the session prompt will re-display. If starting a WIN-OS/2 session from a command line with a "/B" switch, the BOOTLOG.TXT file will show LOADSTART=MOUSE.DRV as the last statement in the file. A look at MOUSE.INI reveals "MOUSETYPE=". That statement MUST equal the type of hardware installed on the system. When running in DOS/WINDOWS, the system will query the hardware attached and update MOUSE.INI accordingly. This is not occurring in OS/2. APAR PJ16247 has been created to address this problem. Until a resolution for the problem of why the MOUSE.INI file is not being updated as it is in DOS/WINDOWS, ensure the MOUSETYPE= statement in MOUSE.INI = <the mouse type described in the boot.description section in syste TITLE: 941115 RUNNING WEB EXPLORER UNDER WARP DESCRIPTION OF SYMPTOMS: You can run Web Explorer under WARP version 3.0 as well as TCP-IP version 2.0 with the base kit service pack for TCPIP 2.0. SUMMARY OF RESOLUTION: The customer will need obtain support from the Internet. DETAILS OF RESOLUTION: If the customer is running Web Explorer they must obtain support from the internet. The support news group on the internet newsgroup is: comp.os.os2.networking.tcp-ip TITLE: 941122 INSTALLING OS/2 WARP, INTERNAL CDROM DRIVE CONNECTED TO A SOUNDCARD DIRECTLY (NOT A SEPERATE CONTROLLER CARD). DESCRIPTION OF SYMPTOMS: Not recognizing cdrom. OS2CDROM.DMD not found. RESOLUTION: This is a hardware related problem. User needs to do the following: On the back of the cdrom drive is a jumper which controls the bus device number. OS/2 install requires it to be on 0 (zero). Most sound board manufacturers leave it at the factory default of 1. If it is anything other than 0, the install disk #1 will not load the driver " OS2CDROM.DMD " and will stop installation with a red screen saying it can't find the cdrom. TITLE: 941123 INSTALLING WARP ON A SYSTEM WITH FUTURE DOMAIN 1680, FIRST PHASE HANG WITH A BLINKING CURSOR. NO LOGO ON THE FIRST REBOOT. DESCRIPTION OF SYMPTOMS: Installing WARP on a system with Future Domain 1680 SCSI controller and Toshiba 3401b CDROM, hang after the first reboot with a blinking cursor on the top left hand corner. No logo, just a black screen with blinking cursor. This is on a 1.5gb Maxtor hardfile. SUMMARY OF RESOLUTION: User has low-level formatted the hardfile under the Future Domain utilities, but did not partition the drive and high-level format under this utilities. The Maxtor drive cylinders set is incorrect, showing 816 instead of actual 1014 cylinders. The hardfile was NOT correctly defined previously therefore causing this problem. DETAILS OF RESOLUTION: Make sure the hardfile is correctly define and format under the Future Domain Utilities to avoid this problem. TITLE: 941123 INSTALLING WARP ON A SYSTEM WITH CDROM (TOSHIBA) CONNECTED TO AN ADAPTEC 1542C, GETTING A RED SCREEN NO CDROM DEVICE SUPPORT FOUND. DESCRIPTION OF SYMPTOMS: Red screen on DISK #1, message no cdrom device support found. RESOLUTION: Under the Adaptec setting option (Ctrl+A), disable the FAST SCSI and Synchronize option. This will enabled OS/2 WARP install DISK #1 to recognize the cdrom. Note: The system has also a SoundBlaster card, but the cdrom (Toshiba) is connected to the Adaptec 1542C SCSI controller. TITLE: 941129 C0000005 ON DISK #1 INSTALLATION OF WARP CS:EIP = 013b : 00000ced CSLIM = 000025ab DESCRIPTION OF SYMPTOMS: Installation of WARP, on Disk 1 received the following error: "A program in this session encountered a problem and cannot continue. c0000005 P1 =00000000 P2 =ffffffff P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000002 EBX=ffe4a814 ECX=00000041 EDX=ffe28c44 ESI=ffe4000a EDI=ff3f0008 DS=03cb DSACC=00f3 DSLIM=000007ff ES=0130 ESACC=00f3 ESLIM=00005133 FS=0000 FSACC=**** FSLIM=******** GS=0000 GSACC=**** GSLIM=******** CS:EIP=013b:00000ced CSACC=00fb CSLIM=000025ab SS:EIP=0017:00000fc6 SSACC=00f3 SSLIM=00000fff EBP=00000433 FLG=00013202 SUMMARY OF RESOLUTION: Check the CONFIG.SYS, user has edited this file and instead of putting " REM " for remarks out the statement, user put a non- alphabet characters. For example, instead of the following: REM basedev=ibm1s506.add user has put ;basedev=ibm1s506.add (a semi-colon " ; ") This above will result the c0000005 error on disk #1. DETAILS OF RESOLUTION: Make sure the user does not use any non alphabet characters for any statements on the config.sys. Under OS/2, everytime a statement needs to be REMarks out, user REM instead of ";" or non alphabet characters. TITLE: 941205 GENERAL PROBLEMS ON INSTALLATION OF WARP, MAINTENANCE DESKTOP OR BEFORE THE FINAL REBOOT DESCRIPTION OF SYMPTOMS: 1. Customer receives sys3175 in os2mm.dll (PJ16290) on first reboot or Maintenance Desktop. 2. Customer receives sys3175 in unpack2.exe, when continuing installation through the maintenance desktop on any diskette. 3. OS2 is unable to operate your hard disk or your diskette drive. 4. System hangs on maintenance desktop. 5. System beeps on diskette #7 when asking for the diskette. RESOLUTION: Remark out the basedev=xxxxxxx.add from config.sys on the harddrive except ibmint13.i13 and ibm%flpy.add and the cdrom controller device driver (Where xxxxxx can be any character and % is replaced by 2 for microchannel system and a 1 if any other system). Also refer customer for possible 174 in Users Guide to OS/2 book additional explanation and actions. If customer has Ethernet Card (NE2000 Compatible), ask to customer to remove it (PJ15955). TITLE: 941103 INSTALLING S3964 DRIVERS ON WARP OS/2 VERSION 3.0 USING S3'S DRIVERS (THOSE WRITTEN BY S3 CORP.) DESCRIPTION OF SYMPTOMS: Problems installing the S3 drivers for the S3 964 chip on system with OS/2 v3.0 1. The install does not finish 2. The install hangs SUMMARY OF RESOLUTION: 1. Edit the S3inst.cmd file 2. Change all references to x:\os2 to x:\os2\boot. (X: = drive where os2 resides) The drivers in original format will not install because the reference the Os2 directory. Os2 v 3.0 installs the drivers into the Os2\Boot directory. DETAILS OF RESOLUTION: 1. Edit the S3INST.CMD file by: a. Place the S3 driver diskette into the disk drive. b. Change to the disk drive c. Pull S3INST.CMD into an editor 2. Change the reference from X:\OS2 TO X:\OS2\BOOT ('X' = drive where OS/2 resides) Note: The drivers in the original format will not install since reference is to the \OS2 directory. OS/2 v3.0 installs drivers into the \OS2\BOOT directory TITLE: 941129 WARP PACKAGE UPDATE - HOW TO FIND OUT WHICH WARP PACKAGE THE CUSTOMER RECEIVED DESCRIPTION OF SYMPTOMS: How to tell which WARP Package the customer is running. SUMMARY OF RESOLUTION: Check the manufactured packages. The SYSINST1.EXE file has been updated. DETAILS OF RESOLUTION: The only file that was changed in the updated WARP Package is SYSINST1.EXE. This file is located on Disk 1 or CD Rom 1 and is installed to: X:\OS2\INSTALL\BOOTDISK\SYSINST1.EXE The old file size for SYSINST1.EXE is 4992 bytes, dated 10-08-94. The new file size for SYSINST1.EXE is 4960 bytes, dated 10-25-94. ************************ The following should be used to distinguish the original GA version of WARP from the updated packages, or from newly manufactured packages. 1. 16-Digit Code on Bottom of WARP Box (1st 6 Digits are Date of Mfg) - If Down-Level (not reworked) will have date prior to 10/29/94 - If Reworked, will have Original Code w/date prior to 10/29/94 PLUS Additional 16-Digit Code that will reflect date of rework - Single 16-Digit Code w/date After 10/29, reflects newly Manufactured Product, w/revised code. 2. Shipping Carton of any "REWORKED" Product will have a single WHITE STICKER (no text) on outside of Box. White sticker will be visible thru pallet. 3. Diskette Label of Diskette 1 has revised Part Number (P/N): 83G8658 (for Diskette Version) 83G8661 (for CD-ROM Version) TITLE: 941130 TRAP000E WITH CS:EIP 0160:FFF6EFBE DESCRIPTION OF SYMPTOMS: Customer receives a Trap000e with cs:eip 0160:FFF6EFBE when running laps WR06000 and/or lan server IP07000. The function name which is failing is _VMGetSem. SUMMARY OF RESOLUTION: Customer must upgrade to the latest csd's for Laps and Lan server. (WR07045 and IP07045) DETAILS OF RESOLUTION: If a customer receives a Trap000E with CS:EIP 0160:FFF6EFBE they must upgrade their Laps to WR07045 and Lan Server to IP07045. NOTE: This may not necessarily pertain to Laps and Lan Server. If the customer is running any other Product such as Novell, other Lan software, or specific drivers make sure they are updated to the latest version. TITLE: 941209 System hangs with Adaptec 2740/2742 controller with cdrom attached. DESCRIPTION OF SYMPTOMS: Attempting to access a CDROM attached to an Adaptec 2740/2742 scsi controller causes trap or system hang. SUMMARY OF RESOLUTION: Disable tagged queing for the AIC7770.ADD driver. DETAILS OF RESOLUTION: 1. Edit the OS2 config.sys file. 2. Change the line BASEDEV=AIC7770.ADD to BASEDEV=AIC7770.ADD /A:0 /TAG:1 3. Shut down system and then reboot for change to take effect. TITLE: 941208 SHUTDOWN FAILS UNDER OS/2 2.11 OR WARP DUE TO LOTUS CC:MAIL BEING ON THE SYSTEM DESCRIPTION OF SYMPTOMS: In some cases, after installing CCMail Client on a system running WARP 3.0, the user will be unable to successfully shutdown. SUMMARY OF RESOLUTION: CCmail is aware of this and the 1.04 build will address this issue. DETAILS OF RESOLUTION: To work around this problem: Make sure the user either has their CCMail folder open, or places a shadow of any object within the CCMail folder on the OS/2 desktop, prior to shutdown. ALSO, word from a Lotus support tech is that if the IN BOX has a shadow on the Desktop, then the problem will not occur. This problem will be addressed in the version 1.04 of CCmail. The most current version of CCMail Client is 1.03 and 1.04 is scheduled to be available early 1995. TITLE: 941207 WARP ERROR MESSAGE "DRIVE X NOT READY PRESS ANY KEY" DESCRIPTION OF SYMPTOMS: CUSTOMERS USING THE BOOT MANAGER FEATURE UNDER OS/2 WARP MAY GET THE ERROR MESSAGE "DRIVE 1 NOT READY PRESS ANY KEY" AND THE SYSTEM BOOTS NORMALLY. OTHER DRIVES NUMBERS MAY ALSO BE REPORTED AS NOT READY. THIS IS MOST PREVALENT ON COMPUTERS THAT UTILIZE A SCSI HOST ADAPTER. SUMMARY OF RESOLUTION: THE CUSTOMER SHOULD CHECK THE HARDWARE SETTINGS OF ALL THE DRIVES IN HIS SYSTEM. ON SYSTEMS WITH SCSI HOST ADAPTERS, BE CERTAIN THAT ONLY BOOTABLE DRIVES HAVE A SCSI ID OF 0 OR 1. USING FDISK FROM A PREVIOUS VERSION OF OS/2 TO INSTALL THE BOOTMANAGER WILL CIRCUMVENT THE MESSAGE. DETAILS OF RESOLUTION: THE ERROR MESSAGE APPEARING IS THE RESULT OF ADDITIONAL MESSAGEING THAT WAS ADDED TO ALERT A USER THAT AN EXTERNAL DRIVE MAY NOT BE POWERED ON. ONE OF THE REASONS THAT IT APPEARS FOR WARP USERS WITHOUT EXTERNAL DRIVES MAY BE A NON STANDARD IMPLENTATION OF THE BIOS IN THE USERS SCSI CARD. USING THE FDISK PROGRAM FROM A PREVIOUS VERSION OF OS/2 WILL STOP THE ERROR MESSAGE FROM APPEARING. FDISK.COM IS LOCATED ON DISK 1 OF MOST VERSIONS OF OS/2 INSTALLATION DISKETTES, IT IS ALSO IN THE \OS2SE21\DISK_2 DIRECTORY OF MOST OS/2 CDROMS. TITLE: 941207 IPE 0160:FFFBA0FC - 000D:000680FC, 1163, 7019 ON DISK 1 INTERNAL REVISION 8.162 94/09/19 DESCRIPTION OF SYMPTOMS: Installing WARP on Disk #1 when the user replaced the IBMKBD.SYS with the size of 29,525, will get the following IPE. *************** IPE 16/32-bit ************************* THE SYSTEM DETECTED AN INTERNAL PROCESSING ERROR AT LOCATION # 0160:fffba0fc - 000d:000680fc 1163, 7019 048600b4 INTERNAL REVISION 8.162 94/09/19 *********** end IPE 16/32-bit ************************ RESOLUTION: User has downloaded the wrong IBMKBD.SYS file. The file size should be 4,677 and dated 7/30/94. Note: this file is the temporarily fix for PJ16077 TITLE: 941209 WHAT IDE CD-ROMS ARE COMPATIBLE WITH OS2 Warp? AND HOW DO I MAKE THEM WORK? DESCRIPTION OF SYMPTOMS: CDROM NOT WORKING UNDER WARP SUMMARY OF RESOLUTION: What Follows is a list of CD-ROMs that are known to be compatible with Warp and how to make them work. DETAILS OF RESOLUTION: The IDE hard disk driver, IBM1S506.ADD, was made aware of ATAPI. This driver will claim all ATAPI devices and mark them as generic devices. The IBMIDECD.FLT filter loads afterwards and scans all drivers for generic ATAPI devices. If it locates one, it will decide if that device is a CDROM. Note: In addition to IBM1S506.ADD and IBMIDECD.FLT, all CD-ROM in the table below require the OS2CDROM.DMD and CDFS.IFS device These are added automatically when the selective install is done. CDROM. An IDE CDROM cannot be a master while a hard drive is being a slave. You cannot use the IBMINT13.I13 for an IDE CDROM. ------------------------------------- Manufacturer |Model | Notes | --------------|-----------|---------| Mitsumi |FX001DE | 1 | ------------------------------------| NEC |CDR-250 | | |CDR-260 | 2 | |NEC 2vi | | ------------------------------------| Sony |55E | 1 | |55D | 1 | ------------------------------------| Panasonic |571 | | ------------------------------------| Wearnes |CDD-120 | | ------------------------------------- Notes: 1. The Mitsumi and Sony cdroms may have problems because they are not ATAPI 1.2 compliant. This should be fixed with updated drivers. 2. NEC 260 cdroms that ship with some Gateway systems adhere to the 1.7 spec instead of 1.2. For these cdroms, the BASEDEV=IBM1S506. A line in the OS2 config.sys file has to be edited as follows: BASEDEV=IBM1S506.ADD /A:x /U:y /ATAPI The /A switch refers to the adapter number that the cdrom is attached to. The /U option references the unit or device number on a particular adapter. The /ATAPI parameter enables ATA Packet Interface protocol for the NEC 260. If the cdrom is attached to the second IDE port or adapter in a system and is the only device on the adapter you would enter: BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI TITLE: 941201 Philips cdrom causes boot problem if /m parameter used DESCRIPTION OF SYMPTOMS: After setting the number of 2500 byte CD frame buffers to a value greater than the default value, OS2 will not boot. The default value is 16, the maximum 26, and the minimum 8. If customer is loading the LMS205.ADD driver, the line in config.sys would read BASEDEV=LMS205.ADD /m:26 to specify 26 2500 byte CD frame buffers. With the Philips 206 cdrom, the line would read BASEDEV=LMS206.ADD /m: SUMMARY OF RESOLUTION: Change the number of CD frame buffers back to the default value. DETAILS OF RESOLUTION: Please follow these instructions: 1. Bring up the OS2 config.sys in an editor. 2. Check the config.sys for the statements BASEDEV=LMS205.ADD /m:26 3. Remove the /m:26 so the line reads BASEDEV=LMS205.ADD 4. Save the file, shutdown and reboot for the changes to take effect. October 25, 1995 Personal Systems Support Family Platform Offering Options ---------------------------------------------------------------------- +--------------------------------------------------------------------+ | Figure 1 (Page 1 of 2). Platform Offering Options | +--------------+-----------------+-----------------+-----------------+ | | SUPPORT LINE | SUPPORT LINE | SUPPORT LINE | | | PER INCIDENT | STANDARD | PREMIUM | +--------------+-----------------+-----------------+-----------------+ | Fees | $190 Per | $4,495 for | $29,995 for | | | Incident | Unlimited | Unlimited | | | | Incidents | Incidents | | | | ($4,050 with | ($28,645 with | | | | certification) | certification) | +--------------+-----------------+-----------------+-----------------+ | Support for | Not Applicable | Priced Per | All products | | Additional | | Product Added | are included | | Products | | | | +--------------+-----------------+-----------------+-----------------+ | Support | 8 AM to 5 PM | 8 AM to 5 PM | 24 X 7 | | Hours | Customer Time | Customer Time | (excluding | | | Zone - Monday | Zone - Monday | Christmas Day) | | | through Friday | through Friday | | | | (excluding U.S. | (excluding U.S. | | | | national | national | | | | holidays) | holidays) | | +--------------+-----------------+-----------------+-----------------+ | 24 X 7 | $260 Per | $1,575 | Included | | Coverage | Incident | additional | | | | | ($6,070 total | | | | | includes the | | | | | base operating | | | | | system)* | | +--------------+-----------------+-----------------+-----------------+ | Priority | Not Applicable | $4,995 | Included | | Handling | | additional | | +--------------+-----------------+-----------------+-----------------+ | Customer | Not Applicable | 2 primary / 2 | 6 primary / 6 | | Contacts | | alternates | alternates | | Included | | | (includes 2 | | | | | primary and 2 | | | | | alternates for | | | | | extended hours | | | | | coverage) | +--------------+-----------------+-----------------+-----------------+ | Additional | Not Applicable | $2,995 each | $2,995 each | | Customer | | | | | Contacts | | | | +--------------+-----------------+-----------------+-----------------+ | Multivendor | Not Applicable | $1,995 | Included | | Coordination | | additional | | +--------------+-----------------+-----------------+-----------------+ | | SUPPORT LINE | SUPPORT LINE | SUPPORT LINE | | | PER INCIDENT | STANDARD | PREMIUM | +--------------+-----------------+-----------------+-----------------+ | Monthly | Not Applicable | Included | Included | | Activity | | | | | Reports | | | | +--------------+-----------------+-----------------+-----------------+ | NOTE: * The charge for Extended Hours Coverage includes the | | OPERATING SYSTEM ONLY. 24 X 7 coverage for each additional | | product is subject to a 35% premium of the cost of support for | | that product, on a product-by-product basis, and must be added to | | the base charge. | | | | A 10% discount will apply for multiple purchases of either Support | | Line Standard or Support Line Premium. Discounts do not apply to | | optional charges. | +--------------------------------------------------------------------+ ************************************************************************ Personal Systems Support Family Fees ---------------------------------------------------------------------- PERSONAL SYSTEMS FORUM o Forum - No charge o IBM TalkLink Fee - $18 per month (plus one-time registration charge of $15) PERSONAL SYSTEMS TECHNICAL CONNECTION PERSONAL SOFTWARE CD-ROM o Single copy - $59 o Annual Subscription - Quarterly updates $119 o Annual Subscription - Monthly updates $299 PERSONAL SYSTEMS CONSULT LINE, PER HOUR (MINIMUM OF 1 HOUR) $240 IBM HOUSE CALL, PER HOUR (MINIMUM OF 2 HOURS) o Hourly - $170 o 2 - 19 Hours - $170 per hour o 20 -99 Hours - $155 per hour o 100+ Hours - $140 per hour CUSTOMER APPLICATION ASSISTANCE, PER HOUR $240 DESKTOP APPLICATION SUPPORT o $64 per Incident o $600 for 10 Incidents TECHNICAL SOLUTIONS Annual Subscription - $50 *********************************************************************** Personal Systems Support Family Single User Services Options ---------------------------------------------------------------------- +--------------------------------------------------------------------+ | Figure 2. Single User Services Options | +--------------+-----------------+-----------------+-----------------+ | | SINGLE INCIDENT | SINGLE INCIDENT | UNLIMITED | | | - 800 # | - 900 # | INCIDENTS | +--------------+-----------------+-----------------+-----------------+ | Contract | Single Incident | Single Incident | Annual | | Period | | | | +--------------+-----------------+-----------------+-----------------+ | Fees | $45.00 Per | $2.00 Per | $179.00 Per | | | Incident | Minute, $50 | Year | | | | Maximum Per | | | | | Incident | | +--------------+-----------------+-----------------+-----------------+ | Standard | OS/2 & DOS | OS/2 & DOS | OS/2 & DOS | | Products | | | (limited | | | | | product set) | +--------------+-----------------+-----------------+-----------------+ | Extended | N/A | N/A | N/A | | Products | | | | +--------------+-----------------+-----------------+-----------------+ | Support | 8AM to 5PM | 8AM to 8PM | 8AM to 5PM | | Hours | Customer Time | Eastern Time - | Customer Time | | | Zone - Monday | Monday through | Zone - Monday | | | through Sunday | Sunday | through Sunday | | | (excluding U.S. | (excluding U.S. | (excluding U.S. | | | national | national | national | | | holidays) | holidays) | holidays) | +--------------+-----------------+-----------------+-----------------+ | 24 X 7 | N/A (Customer | N/A | N/A | | | can purchase | | | | | platform 24 X 7 | | | | | Single Incident | | | | | if required) | | | +--------------+-----------------+-----------------+-----------------+ | Priority | N/A | N/A | N/A | | Handling | | | | +--------------+-----------------+-----------------+-----------------+ | # of | N/A | N/A | Single User, | | Contacts | | | Single License | +--------------+-----------------+-----------------+-----------------+ | Multivendor | N/A | N/A | N/A | | Coordination | | | | +--------------+-----------------+-----------------+-----------------+ | Monthly | N/A | N/A | N/A | | Activity | | | | | Reports | | | | +--------------+-----------------+-----------------+-----------------+ TITLE: 941208 INSTALLING WARP ON VALUEPOINT 6384-199 (P60/D), ON DISK #1 HANGS WITH DISKETTE LIGHT ON AND LOGO DISPLAYED. DESCRIPTION OF SYMPTOMS: Attempting to install OS/2 Warp on ValuePoint 6384-199 (P60/D). Installing from diskettes. Boot from installation diskette, load disk 1 when requested disk 1 hangs with diskette light on and logo displayed. ALT-F2 shows nothing. No driver has been loaded. Turned off int/ext cache and shadowing ROM did not help. RESOLUTION: These ValuePoint systems came with the Flash EEPROM level 0.13.01.AV0M and it has an AMI BIOS. User needs to download VPP60FL6.DSK from the BBS in Raleigh 919-517-0001. The new BIOS is 1.00.06.AV0M. Contact PS/VP Technical support for more informations on getting this new Flash EEPROM upgrade. TITLE: 941212 COULD NOT LOCATE VROBJ.DLL (OS/2 WARP BONUSPAK) DESCRIPTION OF SYMPTOMS: Customer is attempting to run the BonusPak Installation Utility (INSTALL.CMD). The program starts up and issues five "1 file(s) copied" messages and then pops up an error box that states: " BPIU.EXE - COULD NOT LOCATE VROBJ.DLL ". SUMMARY OF RESOLUTION: Somehow the customer's LIBPATH statement has been changed such that the ".;" (dot semicolon) has been deleted from the LIBPATH. The LIBPATH statement in CONFIG.SYS should look similar to this: LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS; continuing on to the end. NOTE: C is drive where OS/2 Warp is installed. DETAILS OF RESOLUTION: If your customer is experiencing this error with the BonusPak Installation Utility, have the customer check his CONFIG.SYS file and look for the .; in the LIBPATH statement. It normally should be the first entry in the list of subdirectories. On a newly installed machine it is the first item. It may however be located anywhere on the LIBPATH= line. Ask the customer if he might have edited this line in his CONFIG.SYS or installed any applications that stated that they were going to edit or update CONFIG.SYS. That will be the way to determine how the line might have gotten modified. OS/2 Warp needs the .; in the LIBPATH to function correctly. A missing .; in the LIBPATH can result in all sorts of errors occurring with different programs of the BonusPak and the system in general. TITLE: 941207 USER MAY GET SYS3175 IN INSTALL.EXE WHILE INSTALLING WARP ON ZEOS PANTERA SYSTEM. DESCRIPTION OF SYMPTOMS: User may get the following SYS3175 in Install.exe during OS/2 3.0 Installation on Zeos Pantera P90 System. . *************** SYS3175 32-bit*************** A program generated an acess violation at 0004d8a9 install.exe 0004:0000d8a9 P1=00000008 P2=000000a0 P3=xxxxxxxx P4=xxxxxxxx EAX=00000000 EBX=00000004 ECX=00000005 EDX=bed80127 ESI=00000d22 EDI=00005628 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0127 ESACC=00f3 ESLIM=00000d22 FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=0027:0000d8a9 CSACC=00fb CSLIM=0000daa9 SS:EIP=008f:0000a7d2 SSACC=00f3 SSLIM=0000d12f EBP=0000a7e8 FLG=00012246 *************** SYS3175 32-bit End *********** SUMMARY OF RESOLUTION: Contact Zeos Technical Support for Bios Upgrade Information. DETAILS OF RESOLUTION: If a system has a Flash Bios Version less than V9.0, user needs to upgrade his Bios to 9.0 which can be downloaded from Zeos Bulletin Board System at 612-362-1219. Once the bios is upgraded, the hard- ware settings for IDE drive in CMOS should be configured as following. Multi Sector = Disable Pre Set = Disable LBA = Enable For more info, please contact Zeos Technical Support. TITLE: 941216 SYS02025 SYS02027 ON THE FIRST REBOOT OF INSTALLATION OF WARP ON A SYSTEM WITH LOCAL BUS IDE CONTROLLER CARD DESCRIPTION OF SYMPTOMS: Installation of WARP, after the first reboot received the SYS02025 and SYS02027 on a Non-IBM systems with a Vesa Local Bus (VLB) IDE controller card. RESOLUTION: Please follow page 178 and 179 of the Guide to OS/2 version 3 manual. If the system has a local bus IDE controller card, DISABLE the BIOS on the 32-bit local bus IDE controller card. Check the system manual for these instructions. TITLE: 950119 SYS3170 WITH CS:EIP C000:00007585 AFTER PRESSING CTRL ESC IN A DOS SESSION RUNNING WARP DESCRIPTION OF SYMPTOMS: Customer receives the following sys3170 error when pressing ctrl esc in a dos session running under Warp: SYS3170 A PROGRAM GENERATED AN EXCEPTION 0162E835 AT 8B26FA76 P1 =26207480 P2 =8B5735C5 P3 =E887B4F8 P4 =3C5F03AE EAX=00006F00 EBX=00000000 ECX=00000000 EDX=00000000 ESI=00000000 EDI=00000000 DS=0000 DSACC=**** DSLIM=******** ES=0000 ESACC=**** ESLIM=******** FS=0000 FSACC=**** FSLIM=******** GS=0000 GSACC=**** GSLIM=******** CS:EIP=C000:00007585 CSACC=**** CSLIM=******** SS:EIP=9FEE:000000DC SSACC=**** SSLIM=******** EBP=00000002 FLG=00020002 SUMMARY OF RESOLUTION: The customer must set their system back to VGA mode (16 colors) if they are running with only 512K of Video Memory. DETAILS OF RESOLUTION: Per page 232 of The User's Guide to OS/2 WARP, Resolution 640 X 480 X 256 requires 1MB of video memory. If the customer only has 512K of Video Memory they MUST set their system back to VGA mode (16 colors) and make sure the config.sys is modified as follows: OLD STATEMENT: DEVICE=C:\OS2\MDOS\VSVGA.SYS NEW STATEMENT: DEVICE=C:\OS2\MDOS\VVGA.SYS TITLE: 950110 USING ALT+F1 ROUTINE UNDER WARP ON A PRELOAD SYSTEM DESCRIPTION OF SYMPTOMS: If a user has a preloaded system and excutes the ALT+F2 command, selecting the maintenance partition (M), some information in the \OS2\BOOT\CONFIG.M file may be incorrect for that particular preload system. If the information is incorrect, when the install program is started, it may exit with an error indicating that the sourcepath incorrect. RESOLUTION: To get around this problem, the user will have to edit the \OS2\BOOT\CONFIG.M file. There are two "set" statements that will need to be changed: SET SOURCEPATH=drive:\path SET FDISKETTESOURCE= 0 or 1; 0 if redirected from cd, remote or local drive 1 if user will be prompted to insert diskettes If the user has not made a set of diskettes using their Diskette Factory program, then SOURCHPATH needs to points to C:\DISKETTS\OS2V3, and FDISKETTESOURCE should equal 0. If the user has made a set of installation diskettes and the install directory tree loaced under \DISKETTS\OS2V3 has been deleted by the Diskette Factory program, then SOURCEPATH should equal A: and FDISKETTESOURCE should be set TITLE: 950118 APTIVA APPLICATION PROBLEMS UNDER WARP. DESCRIPTION OF SYMPTOMS: After installing WARP on Aptiva machines there are a number of problems with the applications that are shipped with the machine. Below are some problems are being identified and fixes: 1. The proper icons for some of the applications is replaced by the OS/2 standard Windows icon. This will be fixed in a future release of OS/2. 2. For Undersea Adventure and Discoverers do the following: a. Edit the file C:\SEA\KA.CNF and change the CDdrive field from E to D and do a change of all the E: to D:. Save the changed file b. Edit the file C:\SEA\SEA.BAT and change of all the E: to D:. Save the changed file c. Edit the file C:\SEA\DISCOVER.BAT and change of all the E: to D:. Save the changed file d. Go to the "Settings" notebook for each of the two programs by doing the following and make the indicated changes: 1) Point the mouse pointer at the icon 2) Press the right mouse button once to get the context menu 3) Move the mouse pointer to Settings and press the left mouse button once 4) Change the "Path and file name:" field from C:\SEA\PS1CDROM.EXE (in the Undersea Adventure) C:\DISCOVER\PS1CDROM.EXE (in the Discoverers) to C:\WINDOWS\PS1CDROM.EXE 5) Press the left mouse button on the "Session" tab 6) Press the "WIN-OS/2 settings button 7) Select the DOS Memory settings 8) Set DOS_HIGH to ON 9) Set DOS_UMB to ON and save the settings 10) Select the button for WIN-OS2 full screen 11) Double click the control box in the upper left corner of the "Settings" notebook to close it. Note: Sound currently does not work for the Discoverers application. This is being worked on. 3. Reuters - When Reuters (Money Network) is started from it's migrated icon or from Windows Program Manager it displays "...not enough file handles..." dialog. Program can not open or create files. The README.WRI file recommends 100 file handles be specifies when running under OS/2. Set DOS_FILES to 100 with the following steps: a. Point the mouse pointer at the Reuters icon b. Press the right mouse button once to get the context menu c. Move the mouse pointer to Settings and press the left mouse button once d. Press the left mouse button on the "Session" tab e. Press the "WIN-OS/2 settings button f. Select the Other DOS settings g. Set DOS_FILES to 100 and save the settings h. Double click the control box in the upper left corner of the "Settings" notebook to close it. 4. The following are some of the problems being addressed. a. Music Mentor gets a General Protection Fault when the "To Session" button is pressed. b. Rapid Resume does not currently work under OS/2 c. Running Disney Software Preview seamless hangs the system TITLE: 950118 APTIVA MACHINES WITH THE ARIA SOUND CARD. (WARP) DESCRIPTION OF SYMPTOMS: The APTIVA machines 530 (2144-66P) & 730 (2144-86P). The ARIA soundcard needs the promethieus driver for OS/2 and it will not be available till 1995. The main symptoms that the user will see is: 1. No sound under OS/2. 2. Windows seamless applications open but disappear and are not in the task list. DETAILS OF RESOLUTION: If the machines equipped with this soundcard (ARIA), the sound MUST be disabled. User must do the following: 1. Go into fullscreen Windows Program Manager 2. Open the "Control Panel" folder 3. Start the "Drivers" program 4. Remove the two ARIA drivers 5. Exit Windows The applications should run seamlessly now TITLE: 950118 INSTALLING WARP ON AN APTIVA, AN IBM PC 300 AND 700 SERIES MACHINES WITH 3.7MB OF MEMORY AND AN IDE CDROM RESULTS IN TRAP0003. DESCRIPTION: Trap 3 can happen on IBM PC 300 Series - 486 Systems , IBM PC 300 Series - Pentium System , IBM PC 700 Series - Pentium Systems and Aptiva machines with 3.7 meg of memory and an IDE CDROM The queueing mechanism in the IDE CDROM driver can cause a trap 3 during install if there is heavy swap activity. A fix must be applied to the OS/2 system to correct this problem. How to apply the fix for a CD install. OS/2 has two diskettes that are required to boot and initiate an install from a CD. The diskettes are called the "Installation" diskette and "Diskette 1". In the fixes sent to you will be a file called IBMIDECD.FLT. Copy this file to "Diskette 1" replacing the original that was on the diskette. Now go forth and do your install as usual. The new module will be used during the install and it will be installed on the final system. How to apply the fix for a diskette install. Boot the Install diskette and go through the first part of install. At the end of the first part of install, a blue screen with white letters comes up telling the user to remove the diskette and press enter to reboot and continue the install. At this time, the user must press the F3 button to get to a command line. In the fixes sent to you will be a file called IBMIDECD.FLT. Copy this file to the directory ?:\OS2\BOOT (? is the drive letter being installed into) replacing the original. Then enter EXIT to get you back to the blue screen. Now go forth and finish your install as usual. the new module will be used during the install and it will be installed on the final system. The fix is AVAILABLE in the APTIVA UPDATE. A replacement disk will be sent. For the CD-ROM version of WARP, a new Diskette #1 will be sent. For the Diskette version, a new Diskette #2 will be sent. Use this new diskette in place of the equivalent diskette that came with OS/2 WARP. TITLE: 950117 UNDOCUMENTED PARAMETER ON THE BOOT COMMAND: BOOT /DOS /N DESCRIPTION: BOOT /DOS /N The /N will do the preparation with the disk, but it does not reboot. User can then do a shutdown as normal. It will shows the following: SYS1716: Warning! You should now restart your system by selecting Shutdown from the desktop, or pressing Ctrl+Alt+Del. EXPLANATION: The program made changes to your hard disk and replaced files C:\CONFIG.SYS and C:\AUTOEXEC.BAT in preparation for the next reset. ACTION: Restart your system by selecting Shutdown from the desktop, or pressing Ctrl+Alt+Del. TITLE: 950119 CDROM in ThinkPad DockII ( using AHA152X ) is not recognized. DESCRIPTION OF SYMPTOMS: On IBM Thinkpad connected to Docking station II with cdrom connected to Adapted 1510,1520,1522 controller is not recognized after installation Trying to do selective install for cdrom system configuration shows no cdrom support which it did during initial installation, when he chooses cdrom as source directory program comes back with message invalid source directory. SUMMARY OF RESOLUTION: PCMCIA drivers takes IRQ 11 on machine and IRQ 11 is default of the Adaptec SCSI adapter (in the docking station) and this IRQ conflict makes cd-rom unusable. DETAILS OF RESOLUTION: Reconfigure SCSI card to IRQ 9 or to any other free IRQ through Dock II setup on bootup ( Control A ). Also Thinkpad has an IDE and on the docking station has a SCSI hard- disk, than move the SCSI driver statements before IDE driver statements in config.sys. TITLE: 941214 COREL DRAW! 3.0 WON'T START UNDER OS/2; GETS ERROR COREL DRAW 3 SECTION DRAWDIR=KEY NOT FOUND IN WIN.INI DESCRIPTION OF SYMPTOMS: When trying to run Corel Draw! 3.0 for Windows under OS/2 the user cannot run the application and gets error, "Corel Draw 3 section drawdir=key not found in WIN.INI." Corel Draw! cannot be run. SUMMARY OF RESOLUTION: 1. Modify WIN.INI file to address missing entry. 2. It may be possible to simply modify the PATH statement in the OS/2 AUTOEXEC.BAT file to include the Corel Draw directory so that the CORELDRW.INI file can be found. DETAILS OF RESOLUTION: 1. Edit the WIN.INI file and add the following: {CorelDraw3. drawdir=C:\CorelDrw NOTE: CorelDraw3 is enclosed in square brackets. Also the directory may be modified as needed. 2. The user may also be able to modify the AUTOEXEC.BAT file of OS/2 so that the PATH statement includes whatever directory Corel Draw! 3.0 is located in, such as C:\CorelDrw as above TITLE: 950117 A:\COUNTRY.SYS IS INCORRECT ON DISK #1 WHEN INSTALLING OS/2 WARP. DESCRIPTION OF SYMPTOMS: Installing OS/2 WARP, on disk #1 encountered " A:\country.sys is incorrect ". RESOLUTION: Check the CMOS. If the user has changed the floppy drives around, make sure the CMOS is setup correctly. Example, if the user switch 1.44mb drive from B to A, and 1.2mb drive from A to B, CMOS must be setup and change that reflect the A drive as 1.44mb and B drive as 1.2mb. Note: Some floppy drives controller has the ability to override the cmos. This means that the card is set for the original setup. For example, if the card is setup for 5 1/4" as A: drive and the user switched the 3 1/2" drive to become A: drive and go into the cmos and change it, when bootup, the card will override the setup on the cmos and still make the 5 1/4" as A:. Advice user to check the controller manual to disable this option on the card. Or refer him/her back to where they bought the controller card. Update: 01/17/1995 TITLE: 941216 OS/2 WARP ENHANCED IDE SUPPORT SYSTEMS WITH NATIVE SUPPORT TRANSLATED BIOS* ENHANCED IDE FEATURE DOS OS/2 DOS OS/2 ----------------------------------------------------------------- DRIVES > 1024 CYL (> 528 MB) BOOT PARTITIONS < 1024 CYL YES YES YES YES ACCESS DISK PAST 1024 CYL NO NO YES YES LOGICAL BLOCK ADDRESSING NO YES NO YES with parameters with parameters for performance /A:0 /U:0 /LBA /A:0 /U:0 /LBA saves drive 3 multiplies FASTER PIO MODE YES YES YES YES DMA ADDRESSING NO NO NO NO not prevalent on controllers advantage for EISA systems only WD UTILITY "ON TRACK" YES ** NA NA provides BIOS translation for system without translated BIOS * IBM Systems with translated BIOS include Valuepoint and IBM Mobile ** On Track will have a OS/2 filter that provides translation at Warp ship. This filter will be shipped with On Track other Enhanced IDE Utilities with WD and IBM hard files for use on systems that do not have translated BIOS. In the meantime we have worked with On Track to have FDISK identify the signature (45H) to prevent corruption. TITLE: 941227 FAXWORKS AND US ROBOTICS SPORTSTER 14400 MODEM DESCRIPTION OF SYMPTOMS: Cannot receive fax Cannot dial Modem not responding SUMMARY OF RESOLUTION: Additional command for modem strings will relieve problems encountered on US Robotics Sportster 14400 modem with fax programs, specifically Faxworks by Softnet. DETAILS OF RESOLUTION: The following is a complete string given by Softnet, which will turn off request to send, and resolve problems with Faxworks, and US Robotics Sportster 14400 modem: &H2&I2&R1S36=0 TITLE: 941213 FLOPPY DOES NOT WORK IN WARP ON NCR 3333 SYS0049 ERROR DESCRIPTION OF SYMPTOMS: Floppy drive does not work in WARP. SYS0049 Error When accessing the A (Floppy) Drive Problems with the Floppy drive on the NCR 3333 DX2/66 SUMMARY OF RESOLUTION: Have A T & T / NCR replace the system board. DETAILS OF RESOLUTION: Replace the system board. NCR acknowledges that this is a hardware problem with the system board (bad IC pack on the system board). This probably occurs on many multi-tasking operating systems including OS/2, NT, and Unix. and Unix. Call A T & T at 800 262-7782 (as of Dec 1994) and ask them to replace the system board due to FLEX DRIVE problems. This is AT&T / NCR Defect Number 86647. TITLE: 950118 TIMING HANG ON IBM PC 300 SERIES - 486 SYSTEMS AND ON ALL APTIVA'S FROM THE 310 (2144-22P) THROUGH THE 530 (2144-66P). DESCRIPTION OF SYMPTOMS: When the IBM PC 300 Series - 486 Systems BIOS code switched CMOS banks, OS/2 (and the physical clock Device Driver) did not know that the CMOS bank was switched. If an IRQ 8 (realtime clock interrupt) came in when the CMOS bank was switched, then the system would hang because the clock DD would read the RTC CMOS locations on the 2nd bank when it should have read them on the 1st bank. The OS/2 virtual DD (VCMOS.SYS) did not allow writes to CMOS with addresses < 0Eh. So, the Rapid Resume data could not be written by a VDM (DOS session or windows). VCMOS.SYS virtualizes ports 70H and 71H. RESOLUTION: VCMOS.SYS will now virtualize ports 22H and 24H when on IBM PC 300 Series - 486 Systems or Aptiva. A fix must be applied to the OS/2 system to correct this problem. How to apply the fix In the fixes sent to you will be a file called VCMOS.SYS. After the install is complete, copy VCMOS.SYS to ?:\OS2\MDOS directory (? is the drive you installed OS/2 into). TITLE: 950118 INSTALLED WARP AND LOST ACCESS TO (ATM) ADOBE TYPE MANAGER 3.0 FOR WINDOWS. DESCRIPTION OF SYMPTOMS: Installing WARP on a sysem with Adobe Type Manager 3.0 will 'backlevel' to ATM ver. 2.5. You will also loose access to any imported fonts already on the system. SUMMARY OF RESOLUTION: Depending on how WARP is installed (bootmanager or dualboot) will determine how to modify the system. 1. Dualboot Installation of WARP will replace the current ATM.INI in the WINDOWS subdirectory. 2. Bootmanager Installation of WARP may point to the x:\psfonts subdirectory partition where it is installed and not to the path in the or in the ATM.INI file. .Setup. PFM_Dir=c:\psfonts\pfm PFB_Dir=c:\psfonts .Settings. ATM=On QLCDir=c:\psfonts Version=3.0 TmpDir=c:\ DETAILS OF RESOLUTION: 1. Dualboot a. Prior to installation of WARP Rename the current x:\windows\psfonts directory to x:\windows\tpsfonts. Rename or backup the current ATM.INI file. Reinstall Adobe Type Manager 2.5, 2.6, or 3. After installation, copy the contents of x:\windows\tpsfonts x:\windows\tpsfonts\pfm to the x:\windows\psfonts and x:\windows\psfonts\pfm directories b. After installation of WARP Rename the current x:\windows\psfonts directory to x:\windows\tpsfonts. Reinstall Adobe Type Manager 2.5, 2.6, or 3.0 After installation, you can add the fonts from the the ATM co panel ADD feature choosing x:\windows\tpsfonts\pfm in the directories window. 2. Bootmanager If Windows is on the same partition that WARP will be install follow proceedure 1a above. If WARP is installed on a differe partition, edit the ATM.INI file to mirror the appropriate li in .SETUP. and .SETTINGS. example above, and reinstall ATM from disks. Note: Applications that are migrated will need the WIN_ATM in t notebook set to on. It may also be necessary to reinstall specia fonts not included with ATM. TITLE: 950117 INSTALLING OS/2 WARP ON A SYSTEM WITH NCR PCI SCSI CONTROLLER THAT USED OS2CAM.ADD, RECEIVED C:\OS2\SYSTEM\COUNTRY.SYS ERROR AFTER INSTALLATION. DESCRIPTION OF SYMPTOMS: Error after successful installation of WARP: " C:\OS2\SYSTEM\COUNTRY.SYS CANNOT BE FOUND " RESOLUTION: User's system is as followed: A clone 486dx2-66mhz, 16mb, AWARD bios version 4.5, PCI system, and a built-in NCR PCI SCSI on the system board. It came with an OS/2 driver called OS2CAM.ADD. User has added in the config.sys on Disk #1 and was abled to install OS/2 thru all the disks, but after reboot, before the desktop, it will display the above error msg. Check the config.sys and the OS2CAM.ADD is in there but the following statement is not in there: BASEDEV=OS2SCSI.DMD. Do the following: Moves the BASEDEV=OS2CAM.ADD after BASEDEV=OS2DASD.DMD. Adds the BASEDEV=OS2SCSI.DMD below the OS2CAM.ADD and reboot. System will boots up and running OS/2 WARP. Please note that this driver is supported only from NCR vendor. It does not come with the OS/2 WARP package. TITLE: 950111 ATAPI.ZIP CONTAIN IBM OS/2 2.X / 3.X IDE CD DRIVER FOR IDE CDROM DRIVES You MUST use these NEW files to replace the existing copies supplied by whatever version of OS/2 you are using. Installation if OS/2 is already installed on your fixed disk ------------------------------------------------------------ 1. you must run Selective Install to install the files for the OS/2 CD-ROM Device Manager and OS/2 CD-ROM File System. a. Open the OS/2 System folder on the desktop. b. Open the System Setup folder. c. Open Selective Install d. Select the CD-ROM Device Support check box e. Select OK f. Scroll to the bottom of the CD-ROM device list table and select the choice OTHER (OS/2 2.1) or Non-listed IDE CD-ROM (WARP) g. Select OK h. Select the OK push button to proceed from the System Configuration screen to the OS/2 Setup and Installation window i. Select Install j. When prompted to do so, insert the numbered installation 2. Copy the files provided in this package OVER those installed in step 1, to their proper location on your system. On Warp this is \OS2\BOOT. Check by doing a 'DIR IBM1S506.ADD /S' on your system <== DIR command 3. IDE CD ROMs that adhere to the ATAPI specification of February 1994 will be detected automatically if they are configured on the Primary or Secondary IDE channel. If your IDE channel is not the primary or secondary, or if your IDE channel is not using the default io ports and IRQs, do a 'HELP IBM1S506.ADD' at an OS/2 command prompt to get detailed information on changing or adding channels. 4. Some drives do not respond to an ATAPI command from the February Spec.These drives can not be auto detected and require an additional parameter on the IBM1S506.ADD line in config.sys. The NEC 260 drive, for example, requires this additional parameter. BASEDEV=IBM1S506.ADD /A:x /U:y /ATAPI where x is the adapter number and y is the unit number. /A: Which IDE drive connector on your adapter contains the cable that the NEC 260 IDE drive is connected to IF you have only one IDE controller, this is Adapter 0, /A:0 IF you have TWO IDE controllers, and the IDE CDROM is connected the second controller cable, this is Adapter 1, /A:1 The Enhanced IDE specifications allow for FOUR adapters, so /A: COULD also be 2 or 3 in your system. /U: Each IDE controller can drive up to TWO drives. If the CD drive is jumpered as the Master then this is unit 0, /U:0 otherwise it is unit 1, /U:1 It is not possible to have a device configuredas Slave without a Master on the same controller. /atapi or /ATAPI This informs the IBM1S506.ADD driver that this unit (/a: /u:) is an ATAPI (IDE attached) CDROM drive... Editing your config.sys... locate the BASEDEV=IBM1S506.ADD line If you have NO parameters on this line, then ADD the parms as defined above, /A:? and /U:? an example line with the CD as slave on controller 1 BASEDEV=IBM1S506.add /A:0 /U:1 /ATAPI IF you ALREADY have parms, and have a /A:? parm already, make sure to add JUST the /U:? parm for that adapter. 5. IF you are using OS/2 2.11 or earlier, you will need to add the following config.sys statement.(If you have WARP, choosing 'NON listed IDE CDROM will cause this line to be placed in config.sys automatically) BASEDEV=IBMIDECD.FLT 6. Shut down and restart your system Installation if OS/2 is NOT already installed on your fixed disk ---------------------------------------------------------------- 1. create the CD install disk 1 from the OS/2 CDROM 2. copy the files supplied here OVER the ones on disk 1. 3. If you have a NEC 260 IDE CDROM drive, edit the config.sys on disk 1 and modify the BASEDEV=IBM1S506.ADD line as described above (adding the /A & /U parms) 3a. If you are using OS/2 2.11 or earlier, add the following statement to config.sys and copy the associated file onto disk 1. BASEDEV=IBMIDECD.FLT 3b. If you are using OS/2 WARP, add the following statement to the config.sys on the DISKETTE 1: SET COPYFROMFLOPPY=1 4. Boot the installation disk and disk 1 and proceed thru installation phase 1. 5. (If you are using OS/2 WARP, skip to step 7) Because the installation program uses copies of these files from a packed file on the installation diskettes, the UPDATED drivers you copied in step 2 are overlayed with the older ones on your hard disk. You MUST manually fix this. When you are asked to reboot to continue the installation, insert the installation disk and press Ctrl-Alt-Del, then through disk 1 to the install panel. Press F3 to get to a command line. Go to the installation drive (wherever you installed OS/2). You will need to clear the read-only attribute on the IBM1S506.ADD file. Do this by typing: (OS/2 2.1 & 2.11) /os2/attrib -r \os2\ibm1s506.add Copy the updated files (OS2CDROM.DMD, IBM1S506.ADD, and IBMIDECD.FLT from disk 1 to the proper location on the install partition) 6. type EXIT from the command line 7. remove the diskette from A: and reboot 8. Complete the rest of install ****************** NOTE: This is a README.TXT file from this ATAPI.ZIP package available on the IBM BBS 919 517 0001. Is is on LIB #17 OS/2 Device Drivers. Also under the SAME name on CIS and other BBS's. ATAPI.ZIP 45862 12-29-94 OS/2 2.x/3.x IDE TITLE: 950111 WIN32S SUPPORT LIMITATIONS UNDER OS/2 3.0 WARP DESCRIPTION OF SYMPTOMS: Versions of WIN32S above 1.1 are not supported under OS/2 V3.0 SUMMARY OF RESOLUTION: Check the version of WIN32S DETAILS OF RESOLUTION: Any application which utilizes the 32 Bit API library "WIN32S" installs the version necessary for the application to run. A WIN32S.INI file is placed in the WINDOWS\SYSTEM directory and in it, the version of WIN32S is revealed. The README found in the root directory documents support for WIN32S being at versions 1.0 and 1.1. If the installed version is greater than 1.1, it is not supported. TITLE: 950116 INSTALLING WARP AFTER THE FIRST PHASE, GET ERROR MESSAGE " OS2KRNL IS NOT ACCEPTABLE ... " DESCRIPTION OF SYMPTOMS: OS2KRNL is unacceptable on the first reboot when installing WARP on system with a Micropolis 2112mb SCSI drive. It is connected to a Future Domain card. RESOLUTION: Users need to contact Micropolis for assistance getting an upgrade ROM for this 2gb drive to work under OS/2 WARP TITLE: 950116 OS/2 WARP NOT RECOGNIZING SONY 31A CDROM WHICH IS ATTACHED TO A CARDINAL DSP16 (SOUNDBLASTER COMPATIBLE) DESCRIPTION OF SYMPTOMS: OS/2 WARP does not recognize the SONY 31A which is connected to the Cardinal DSP16 card. Installation asks for the CD but keeps looping and ask for the CD again and again. SUMMARY OF RESOLUTION: User is using downloaded driver (SONY31A.ADD) and followed the parameter from page 329 example 4 of the user's guide. As default, the sound port address is 220h and IRQ 5. The CDROM is set for port address 300 and IRQ 12. User should use the driver that came with OS/2 WARP and added the following to the SONY31A.ADD statement: SONY31A.ADD /A:0 /AT:05 /P:0300 /I:12 /V where the port address and irq above should be for the cdrom, NOT the soundcard. The /P: is the address of the cdrom and the /I: is the IRQ of the CDROM drive. (the /v only showed us if the cdrom was recognized when the driver loaded or not). Note: the above problem is happen if user put the wrong port address and irq for the cdrom. TITLE: 950116 INSTALLATION OF WARP, IT DOES NOT RECOGNIZE CDROM SONY 541 WHICH IS CONNECTED TO A FUTURE DOMAIN 1600 SERIES SCSI CARD DESCRIPTION OF SYMPTOMS: WARP does not recognize the Sony CD-ROM which is connected to the Future Domain 1600 ( FD16-700.ADD ). RESOLUTION: This SONY 541 is SCSI II type CD-ROM. It is compatible and work with the FD16-700.add device driver. Users need to make sure the SCSI ID for the SONY is NOT 0 or 1. In this case, user has changed the ID to 2 and WARP is abled to recognize the SONY CD-ROM. TITLE: 950116 USING STACKER V1.1 FOR OS/2 UNDER WARP DESCRIPTION OF SYMPTOMS: Systems extended logical partitions are not being recognized by WARP This is because the drives are stacked, using Stacker software. RESOLUTION: Called Stacker to get the lastest info on their version 1.1 for OS/2. Stacker stated that in order for Stacker for OS/2 1.1 to work proper with WARP users need to download and install a fix ( SWARP.EXE ) from their BBS (619) 431-5956. Their technical support number is (619) 929-3900. TITLE: 950111 SYSTEM HANGS ON THE FIRST REBOOT WITH TRAP0003 CS : EIP = 0568 : 00002913 and CSLIM = 00002aa8 ( WARP ) DESCRIPTION OF SYMPTOMS: TRAP0003 on the first reboot installing OS/2 WARP. ********************* TRAP 32-bit *********************** TRAP =0003 ERRCD=0000 ERACC=**** ERLIM=******** EAX =00000000 EBX =007601a8 ECX =fdf10358 EDX =000005a8 ESI =00000358 EDI =fc8005a8 EBP =00004dcc FLG =00003002 CS:EIP=0568: 00002913 CSACC=009b CSLIM= 00002aa8 SS:ESP=0030:00004dc6 SSACC=1097 SSLIM=00003fff DS =0570 DSACC=0093 DSLIM=000002d2 CR0 =8001001b ES =0030 ESACC=1097 ESLIM=00003fff CR2 =feda4000 FS =0000 FSACC=**** FSLIM=******** GS =0000 GSACC=**** GSLIM=******** ERROR AT LOCATION # 0160:fff5c34c - 000d:a34c 60000, 9084 048600b4 INTERNAL REVISION 8.162 94/09/19 Failure Mode : Installing WARP first reboot. ***************** end TRAP 32-bit **************** RESOLUTION: This is related to the ATAPI fix for IBM 2.x /3.x IDE CD driver for IDE CDROM drives (PDDB FFWFC). User has an IDE NEC 260 CDROM. Downloaded ATAPI.ZIP from our BBS. Please follow the README.TXT. (919 517 0001) Bootup the Installation disk and F3 out on Disk #1 at the Easy/Advance screen. This will get to the CDROM prompt (ie F:\OS2IMAGE\DISK1 where F is the cdrom drive, assuming this is a cdrom installation). Go to the drive where WARP is installed (ie C: ) and change to \OS2\BOOT subdirectory. Check the file IBM1S506.ADD. It should be dated 11/18/94 and size is 27312. If not, it is an older file. Check to see if IBM1S506.ADD is NOT Read Only (using DIR /AR). If the attribute shown Read only, user must use the ATTRIB command to take off the Read only attribute. ATTRIB.EXE has not been unpack during the first phase of install, user must unpack this file. It is on Disk #12 and is packed (ATTRIB). Go to \OS2 subdirectory and execute the following command: UNPACK F:\OS2IMAGE\DISK12\ATTRIB This should unpack ATTRIB.EXE to \OS2 subdirectory. Go to \OS2\BOOT subdirectory and execute the following command to take the Read only off the IBM1S506.ADD: ATTRIB -R IBM1S506.ADD Copy the new IBM1S506.ADD to this \OS2\BOOT subdirectory. Take out the disk on drive A: and reboot and continue with the second phase of the installation. This section contains a collection of all the README files included with OS/2 Warp version 3 and its BonusPak applications. OS/2 WARP VERSION 3 README Welcome to OS/2* Warp Version 3 (OS/2 Warp). This README contains the latest information available. It also contains helpful hints found in our testing. The README is only one source of information provided with OS/2 Warp. Greater detail can be found in: o User's Guide to OS/2 Warp o Using OS/2, a new tutorial o The Information Folder located on the Desktop, which provides new online books to help you learn and develop skills using OS/2 Warp: - Master Help Index - Command Reference - REXX Information - Multimedia - Printing in OS/2 - Performance Considerations - Application Considerations - Windows Programs in OS/2 The Application Considerations online book, for example, contains helpful hints on running games under OS/2 Warp. The Printing in OS/2 online book helps with installing new printers or solving problems. These are a few of the many items found in the new online books. To help you locate information in this README, you can use the Find option in the Edit menu of the OS/2 System Editor. You can print the file by dragging it to your printer object or by using the Print choice on the pop-up menu. CONTENTS ________ 1.0 Creating Diskette Images from the OS/2 CD 2.0 Enhanced IDE Hard Drives Greater than 528MB 3.0 Multiple Versions of Windows** 4.0 Win32s** Versions 1.0 and 1.1 Applications 5.0 Repetitive Sounds or No Sound After System Installation 6.0 Desktop Settings Notebook 7.0 Monochrome Monitors 8.0 Lotus** Notes Does Not Support Comet Cursor 9.0 Lotus Approach 3.0 Needs to Have Memory Setting Adjusted 10.0 Pen for OS/2 11.0 Startup Warning Message 12.0 Changing Display Resolution Using the System Object 13.0 Trademarks 1.0 CREATING DISKETTE IMAGES FROM THE OS/2 CD _________________________________________ To create diskette images from the OS/2 CD after OS/2 Warp has been installed, you must first find out how many diskettes you will need. Follow these procedures: 1. Place the OS/2 CD in the CD-ROM drive. 2. Type DIR X:\DISKIMGS\OS2\35 /W (where X: is the CD-ROM drive) and press Enter. 3. When a list of files appears on your screen, count the files that end with the .DSK extension. Each .DSK file requires one formatted diskette. Use the following command to create each diskette image: X:\DISKIMGS\XDFCOPY X:\DISKIMGS\OS2\35\diskname.dsk A: where: X: Is the drive letter of the CD-ROM drive. \DISKIMGS\XDFCOPY Is the location and name of the program used to create the diskettes. \DISKIMGS\OS2\35 Is the location of the files containing the diskette images. DISKNAME.DSK Is the diskette image file name (for example, DISK0.DSK). A: Is the drive letter of your 3.5-inch diskette drive. For example, to create the Installation Diskette (DISK0.DSK), type the following and press Enter: X:\DISKIMGS\XDFCOPY X:\DISKIMGS\OS2\35\DISK0.DSK A: (where X: is the CD-ROM drive and A: is the diskette drive.) 2.0 ENHANCED IDE HARD DRIVES GREATER THAN 528MB ___________________________________________ If you have an Enhanced IDE hard drive that has a capacity of greater than 528MB (greater than 1024 cylinders), note the following restrictions: The FAT file system is limited to partition sizes of less than 1024 cylinders. The HPFS file system can support data partitions that are greater than 1024 cylinders. However, the partition from which OS/2 is started cannot be greater than 1024 cylinders. The HPFS file system can support drives up to 2GB. 3.0 MULTIPLE VERSIONS OF WINDOWS ____________________________ OS/2 Warp does not support multiple versions of Windows (for example, Windows 3.1 on drive D and Windows for Workgroups** 3.1 on drive E) or multiple installations of the same Windows version (for example, Windows 3.1 on drive D and Windows 3.1 on drive E). 4.0 WIN32S VERSIONS 1.0 AND 1.1 APPLICATIONS ________________________________________ Install your Win32s applications in a WIN-OS/2* Full-Screen session. You can then run your Win32s applications in either a WIN-OS/2 Window or Full-Screen session. 5.0 REPETITIVE SOUNDS OR NO SOUND AFTER SYSTEM __________________________________________ INSTALLATION ____________ If your computer produces unusual or repetitive sounds, or no sounds at all, after you have installed OS/2 Warp, you might have a mismatch between the device driver parameters supplied by OS/2 and the sound adapter card or the BIOS setting of your computer. To determine if this situation exists, use the RMVIEW utility program to display the OS/2 device driver types and parameters installed on your computer. The program quickly scrolls through the device types. The audio card is in the last section of the devices. 1. Open an OS/2 Window or Full Screen session. 2. Type the following: RMVIEW (press Enter) 3. Note the following parameters (where X will be replaced by a value): I/O = 0X0XXX IRQ Level = X DMA Channel = X These are the parameters that OS/2 is using for your audio device. 4. Refer to the hardware documentation that came with your audio card to determine the hardware settings of your audio card. Note the following parameters: Port address or I/O = 0X0XXX Interrupt level or IRQ Level = X DMA Channel = X 5. If hardware and software settings are not the same: a. Select OS/2 System from the OS/2 Desktop. b. Select System Setup. c. Select Selective Install. d. Select the Multimedia Device Support icon. The Device Selections and Settings window appears. The audio card appears in the Devices(s) in System to be Installed window. e. Select the Device Settings push button. A window appears with your port address, DMA, and Interrupt Level settings. f. Select the values that match the hardware settings for your audio card. Then select OK. g. When the Device Selections and Settings window reappears, select OK. h. When the System Configuration screen reappears, select OK. i. At the OS/2 Setup and Installation screen, select Install. j. When the Source Directory window appears, select Install. k. Follow the instructions that appear on your screen. 6. Shut down and restart your computer so that these changes will take effect. If the sound problem continues, there might be a conflict with the BIOS settings of your computer. To determine if this condition exists, you will need: o The hardware utility diskette for your computer o The documentation that came with your computer When you have the diskette and documentation, follow these steps to determine the hardware configuration: 1. Insert the hardware utility diskette into drive A. 2. View the BIOS settings that are configured for your computer. Refer to your hardware documentation for details about viewing this information. 3. Compare the IRQ Level from the RMVIEW utility program display with the hardware IRQ or Interrupt Level found in the hardware documentation. If the hardware IRQ or Interrupt Level for the LPT port is set to enable at 5 or 7, disable it. Refer to your hardware documentation for details about disabling and saving the new settings. NOTE: OS/2 Warp parallel printing no longer requires an IRQ setting. If you experience unusual sounds in a WIN-OS/2* session, refer to the online help contained in the Multimedia book located in the Information folder on your Desktop. 6.0 DESKTOP SETTINGS NOTEBOOK _________________________ When using the Archive page of the Desktop Settings notebook, specify a drive that is managed by the same file system as the drive on which your Desktop resides. For example, if your Desktop is managed by the FAT file system, do not specify a drive for an Archive location that is managed by HPFS. Use the FDISK OS/2 command to display the file system of the drive on which your Desktop resides. The file system is displayed in the FS Type field. 7.0 MONOCHROME MONITORS ___________________ If you are using a laptop computer (such as the IBM* ThinkPad* 750 or 750P) with a monochrome display and the Western Digital** display driver is installed, you might experience problems with the way the cursor is displayed. For example, when you use Alt+Esc to switch from a full-screen session to the OS/2 Desktop, the cursor might appear completely black until it is moved. In addition, changing the size of a window with the mouse can leave a trail of discolored pixels as the cursor moves. These problems do not occur on an external color monitor or when the VGA driver is installed. 8.0 LOTUS NOTES DOES NOT SUPPORT COMET CURSOR _________________________________________ You cannot use the OS/2 Warp Comet Cursor with Lotus Notes. 9.0 LOTUS APPROACH 3.0 NEEDS TO HAVE MEMORY SETTING _______________________________________________ ADJUSTED ________ To use Lotus Approach 3.0, change the DOS memory setting DPMI_MEMORY_LIMIT from 64 to 10 before you run the application. Do the following: 1. Display the pop-up menu for the Lotus Approach 3.0 object, the WIN-OS/2 Window object, or the WIN-OS/2 Full Screen object. 2. Select Settings. 3. Select the Session tab. 4. Select the WIN-OS/2 Settings push button. 5. Select the last radio button, All DOS and WIN-OS/2 settings. 6. Select OK. 7. Scroll down to DPMI_MEMORY_LIMIT and select it. 8. Change the value from 64 to 10. Then select the Save push button. 9. Close the Settings notebook. 10.0 PEN FOR OS/2 ____________ When you are installing or reinstalling Pen for OS/2, you might receive the following message: SYS1059: The system cannot execute the specified program. If you receive this message, you must apply a fix to the Pen installation program. 1. Install the PATCH utilities: a. Select OS/2 System. b. Select System Setup. c. Select Selective Install. d. Select OK on the System Configuration window. e. Select Serviceability and Diagnostics Aids. f. Select Install from the OS/2 Setup and Installation window and follow the instructions on the screen. 2. To apply the fix to the Pen for OS/2 installation program, follow these steps: o If you are reinstalling Pen for OS/2: a. Copy the PEN.DAT file, which is located in the \DISK10 directory on the OS/2 CD-ROM, to the drive and directory where you have Pen for OS/2 installed. b. Change to the drive and directory where you have Pen for OS/2 installed. At an OS/2 command prompt, type: PATCH PEN.DAT /A (press Enter) o If you are installing Pen for OS/2 for the first time: a. Copy the PEN.DAT file, which is located in the \DISK10 directory on the OS/2 CD-ROM, to the PEN for OS/2 Diskette 1. b. Insert the Pen for OS/2 Diskette 1 into drive A. c. From an OS/2 command prompt, switch to drive A, and type: PATCH PEN.DAT /A (press Enter) A message is displayed confirming that the fix has been applied. 3. Install Pen for OS/2. 11.0 STARTUP WARNING MESSAGE _______________________ If you select the option to archive system files from the system settings page of your Desktop, you might receive the following warning during system startup: There may not be enough room at the target to create an archive. Do you wish to continue? This message is generated to inform you that there will be less than 10MB of free space available in the selected archive hard disk partition after the archive is performed. If you select Yes, the archiving process will continue. If you select No, the archiving process will not be performed. 12.0 CHANGING DISPLAY RESOLUTION USING THE SYSTEM OBJECT ___________________________________________________ You can use the System object to change the resolution for many of the display drivers supported by OS/2. Do the following: 1. Open OS/2 System on your Desktop. 2. Open System Setup. 3. Open System. 4. Select the Screen tab. If the Screen page says "Page 1 of 2" at the bottom, go to page 2 and select your display from the list. If the Screen page does not have a page 2, go to step 5. 5. Select the screen resolution that is supported by your display from the Screen resolution list. (Refer to the documentation that came with your display for a list of supported resolutions.) 6. Close the System object, shut down OS/2, and restart your computer so that these changes will take effect. 13.0 TRADEMARKS __________ The following terms, denoted by an asterisk (*) in this README file, are trademarks of the IBM Corporation in the United States or other countries: o IBM o OS/2 o ThinkPad o WIN-OS/2 The following terms, denoted by a double asterisk (**) in this README file, are trademarks of other companies as follows: TRADEMARK OWNER Lotus Lotus Development Corporation Microsoft Microsoft Corporation Windows Microsoft Corporation Windows for Workgroups Microsoft Corporation Win32s Microsoft Corporation Western Digital Western Digital Corporation THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. (C) Copyright IBM Corporation 1994. All rights reserved. OS/2 WARP VERSION 3 INSTALLATION README Welcome to OS/2* Warp Version 3 (OS/2 Warp). OS/2 Warp does a lot of the work involved in installing an operating system for you, and includes the following improvements: o It takes less time and fewer diskettes to install. o It automatically installs the Dual Boot feature when you install over DOS. o You can install more than one printer during the initial installation. We hope you find installing OS/2 Warp to be a quick and easy process. This README contains the latest information available about installing OS/2 Warp. You can also find additional information in the "User's Guide to OS/2 Warp." CONTENTS _________ 1.0 Format Errors when Installing OS/2 on 4MB Computers 2.0 Note to Users of NetWare Client Version 2.10 for OS/2 3.0 Video Screen Problems 4.0 Note to Users of a ThinkPad with a Docking Station or a PS/2 Model 76 5.0 Note to Users of a ThinkPad 720 6.0 Trademarks 1.0 FORMAT ERRORS WHEN INSTALLING OS/2 ON 4MB COMPUTERS ___________________________________________________ When installing OS/2 on some 4MB computers, you might not be able to format the installation partition. You will see the following error message: Disk Format Error If so, discontinue the OS/2 installation and do the following: 1. Insert the DOS Setup diskette 1 from a DOS package into drive A. 2. Turn on your computer. If your computer is already on, press Ctrl+Alt+Del to restart it. 3. When the DOS Setup screen appears, press F3 to display a command prompt. 4. Use the DOS FORMAT command to format the partition you want to use to install OS/2. Refer to your DOS documentation for information about the FORMAT command. 5. Begin the OS/2 installation again. If the Installation program asks if you want to format the installation partition, select Do Not Format the Partition. 2.0 NOTE TO USERS OF NETWARE CLIENT VERSION 2.10 FOR OS/2 ________________________________________________________ Be aware of the following before installing OS/2 Warp: o The LOGIN.EXE command can no longer be executed from the OS/2 CONFIG.SYS file. To correct this situation, move the LOGIN.EXE command to the STARTUP.CMD file. o If your configuration requires that you execute the LOGIN.EXE command from the CONFIG.SYS file, contact your NetWare** support line to obtain special versions of NWDAEMON.EXE and SPDAEMON.EXE. 3.0 VIDEO SCREEN PROBLEMS _______________________ The OS/2 Installation program automatically detects the graphics adapter or chip in your system. However, if the refresh rate for the resolution you have chosen is configured incorrectly, you might experience problems such as: o The Desktop is compressed into a narrow horizontal band. o Multiple images of the Desktop are visible. o Diagonal lines fill the Desktop. To configure the refresh rate, use the configuration utility program that came with your graphics adapter or system. Follow the instructions supplied by the manufacturer to set the screen refresh rate. (In many cases, the utility must be run under DOS.) When you are finished running the configuration utility program, shut down and restart OS/2 so that the changes will take effect. If you are unable to run the configuration utility program for your graphics adapter or system, try one of the following: o Restart your computer and press Alt+F1 when a small white box appears in the upper-left corner of your screen. Then select V to reset your system to VGA mode. o If you can see enough of the screen to use the mouse, open the System Object (in the System Setup folder) and select a lower resolution on the Screen page. Then close the System Object, shut down OS/2, and restart your computer so that the changes will take effect. 4.0 NOTE TO USERS OF A THINKPAD WITH A DOCKING STATION _____________________________________________________ OR A PS/2 MODEL 76 __________________ If you are installing OS/2 on an IBM PS/2* Model 76 or an IBM ThinkPad* attached to a docking station, you must follow the instructions in "User's Guide to OS/2 Warp" before you begin the installation. (These instructions are described in the section titled "Using an IBM ThinkPad with a Docking Station or an IBM PS/2 Model 76.") If you are installing on a 240MB or 340MB hard disk that uses the IBM2HDSK.ADD device driver, you must follow the additional steps listed below. These steps should be performed after you complete step 13 in the procedure described in "User's Guide to OS/2 Warp." 1. Remove any diskette from drive A and insert OS/2 installation Diskette 1. 2. Copy the file IBM2HDSK.ADD onto OS/2 installation diskette 1. 3. Edit the CONFIG.SYS file. If you have an ASCII text editor installed, you can use it to edit the CONFIG.SYS file. Otherwise, you can use the editor that comes on the OS/2 installation diskettes by typing TEDIT CONFIG.SYS at the OS/2 command prompt. 4. Add the following line as the first of the BASEDEV entries in the CONFIG.SYS file: BASEDEV = IBM2HDSK.ADD 5. Save the changes to CONFIG.SYS and continue with installation. After installation is finished, make sure that file IBM2HDSK.ADD is in the OS2\BOOT directory, and that the line BASEDEV=IBM2HDSK.ADD is in your CONFIG.SYS file. 5.0 NOTE TO USERS OF A THINKPAD 720 _______________________________ On a ThinkPad 720, install OS/2 Warp using only the internal LCD screen if you plan to run OS/2 Warp without an external monitor attached at any time. If you install OS/2 Warp with an external monitor attached, you need to rebuild the .PMI in order to run without the external monitor. 6.0 TRADEMARKS __________ The following terms, denoted by an asterisk (*) in this README file, are trademarks of the IBM Corporation in the United States or other countries: IBM OS/2 PS/2 ThinkPad The following terms, denoted by a double asterisk (**) in this README file, are trademarks of other companies as follows: Trademark Owner NetWare Novell, Inc. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. (C) Copyright IBM Corporation 1994. All rights reserved. README for Multimedia Viewer Release 1.0 (c) Copyright IBM (R) Corp. 1994 This README contains information about the IBM Multimedia Viewer, a versatile tool for organizing multimedia data objects. This "Light Table" folder is designed to look like a photographer's light table containing picture slides, with the added benefit of being able to play audio and video files. Enjoy. IBM Multimedia Viewer Quickstart ________________________________________________________________ o To start the media browser for an object in the Multimedia Folder, simply double-click on the SLIDE FRAME (the border) of the object. o Please read the following sections which explain some Multimedia Viewer and OS/2 Workplace Shell capabilities. For example, you will learn how you can start a Workplace Shell application by double clicking on the middle of the object. IBM Multimedia Viewer Features ________________________________________________________________ o The Multimedia Viewer product provides the ability to manage and view multimedia objects, such as image, video, animation, audio, and text files. o The Light Table folder provides all the features of a standard OS/2 folder, with a number of additions. Objects in a Light Table Viewer appear as if they were photo slides on a photographer's light table. o Slides are created when multimedia objects are moved or copied into a Light Table folder. Slides are also created for Light Table References (see below). About Light Table Browsers ________________________________________________________________ o Light Table folders provide browsers for reviewing your multimedia data. There are four browsers: Audio, Video/Animation, Image and Text. o The Audio, Video/Animation and Image browsers can be invoked by positioning the mouse pointer anywhere over the SLIDE FRAME and double-clicking the left mouse button. Large images may take a while to appear on your display. o If the mouse is located over the middle of the object (not the border), double-clicking the left mouse button will behave as it normally does in a standard OS/2 folder. o The Text browser can be invoked by double-clicking on the text object. o The browsers will work with any file type supported by the OS/2 Multimedia system. See your OS/2 documentation for more information on supported file formats. Creating a new Light Table folder ________________________________________________________________ Light Table folders are created in the same manner as standard OS/2 folders. After installing the Multimedia Viewer, open the Templates folder and locate the Light Table template. Drag/Drop the Light Table Template to the desired location on your desktop. Adding New Files to your Light Table ________________________________________________________________ The preferred method of adding multimedia data objects to a light table folder is to create a "Light Table Reference". Follow the steps below. o Find the data object you wish to use by opening its folder. o Click the right mouse button on the data object to bring up the object's popup menu. o Select "Create LT Reference" from the popup menu. o Select the Light Table folder in which you want the data object to appear. Only Light Table folders can be selected. A miniature slide for the data file should now be visible in your Light Table folder. Additional Light Table Reference Object Tips ________________________________________________________________ o Light Table Reference objects are similar to Shadow objects. They are a reference to another object or file. Unlike Shadow objects: - References provide storage for slide images. - References are preserved when the parent object is not present. These features allow Light Table References to display slides in a Light Table folder even when the parent object is removed. For example, if a CD-ROM containing an image is removed, the image slide will remain in the Light Table. o When selecting multiple objects to create Light Table References, do not mix .BMP files or .ICO files with other data file objects. You can select all .BMP files as one group, then create Light Table References for these selected objects. Select all .ICO files as another group to create Light Table References. Then select all the rest of the objects to create Light Table References. o When you double click the center of objects in the Light Table, the OS/2 Workplace Shell will launch any application in OS/2 that has an association with that filetype. For example if you double click on an OS/2 .BMP file, you will launch the OS/2 Icon Editor. A file type will be associated to any application that supports it if the application has set up the association. Installation Notes ________________________________________________________________ The Multimedia Viewer is installed on the same drive as the OS/2 Multimedia \MMOS2 directory, and requires about 1.3 MB of disk space. If this drive is the one that is used by the OS/2 swapper, this reduces the amount of swapper space available for the system. In this case, you may want to change the drive used for the OS/2 swapper to one containing more space. Refer to the SWAPPATH statement in the Command Reference information (in the Information folder on your desktop) for more details about determining and changing the location of the OS/2 swapper file. TRADEMARK INFORMATION ________________________________________________________________ IBM and OS/2 are registered trademarks of International Business Machines Corporation. README FILE FOR OS/2 3.0 Utility Diskettes _____________________________________________ August 1994 This file contains additional information about using the Utility Diskettes. You can use the Utility Diskettes to: o Start OS/2* 3.0 from diskettes o Back up and restore your system o Check the hard disk for errors or problems o Format a diskette or the hard disk USING BACKUP AND RESTORE The BACKUP and RESTORE files on Utility Diskette 3 allow you to back up and restore your entire hard disk. BACKING UP YOUR SYSTEM You can use the BACKUP file on Utility Diskette 3 to back up your system. BACKUP copies the files from the hard disk to diskettes. A complete backup of your system requires about 50 blank formatted, high-density (2MB) diskettes for OS/2 and based on other software installed an additional diskette for each 1.44 megabytes of files. Make backup diskettes of your system as it was originally shipped. Backup diskettes allow you to restore your system, if the hard disk is ever damaged. For informatoin on using the backup program refer to your Users Guide or Concise Publication. RESTORING YOUR SYSTEM Use the RESTORE file on Utility Diskette 3 to restore your system. RESTORE copies files from the backup diskettes to your hard disk. If you ever need to restore the backup diskettes to your hard disk, make sure you know if your hard disk has a formatted partition. If the hard disk (drive C) has a formatted partition, follow the instructions for the restore utility described in the OS/2 Users Guide or Concise Publication. If the hard disk does not have a formatted partition, create a partition and format the partition before proceeding with the restore procedure described in the booklet for your system. Use FDISK to create a partition and FORMAT to format the partition. The FDISK and FORMAT command files are on Utility Diskette 3. TRADEMARKS AND SERVICE MARKS ____________________________ Terms denoted by a single asterisk in this file (*) are trademarks of the IBM Corporation in the United States and/or other countries. These terms include: OS/2 IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. Copyright IBM Corporation, 1993, all rights reserved. IBM Internet Connection for OS/2 Welcome to the IBM Internet Connection for OS/2. This README contains the latest information available. For an overview of this package prior to installation, refer to the BonusPak User's Guide. After installation, you can get an introduction and information on how to use these applications by opening the IBM Internet Connection for OS/2 folder and clicking on the Introduction to the IBM Internet Connection icon. IBM OS/2 World Wide Web client software available ------------------------------------------------- Once you have connected to the Internet with this package, you can download IBM's OS/2 World Wide Web client, WebExplorer. Initially this will be a pre-release version. The final version will also be available for download along with any updates to other applications in this package. To access these updates, open the IBM Internet Connection for OS/2 folder and click on the Retrieve software updates icon. Click on the help button for details on getting the updates. If you already have a TCP/IP package ------------------------------------ IBM does not support running TCP/IP applications across both a LAN and Internet connection. The supported environment allows either a LAN TCP/IP product to be installed -or- an Internet TCP/IP product to be installed. It is recommended that you remove the LAN TCP/IP product before you install the Internet TCP/IP product. Modem speed ----------- The modem speed defaults to 9600 for all modems. If you have a 14,400 bps (or 14.4K) modem, you will want to specify a speed of 38400 or 57600. The maximum data rate that your modem can accept is usually documented in the handbook or reference material which accompanied your modem. If your modem is a 9600 bps modem, you should specify 9600. Ultimedia Mail/2 'Lite' ---------------------- There is a Read Me icon in the UltiMedia Mail/2 'Lite' folder under the information icon. Please refer to it before using mail. Image and audio support using Gopher ------------------------------------ The Gopher application uses external viewing programs for image and audio support. By default, Gopher will use the viewing programs that are part of the Multimedia Viewer package in the BonusPak. Therefore, in order to get image and audio support in Gopher you will need to install the Multimedia Viewer package. DOS and Windows TCP/IP Programs ------------------------------- You can run Windows Sockets compliant Windows TCP/IP programs with this package. This requires that you have Windows installed and that you install the WIN-OS2 support of OS/2. Restoring your Internet Connection Desktop ------------------------------------------ In rare instances, you may find that the Internet Connection folder or the icons in it, are lost or scrambled. To recover, run the program IFOLDER from the OS/2 command line, and your folders and icons will be restored. If you find that some icons are still not working as they should, delete the Internet Connection folder and all its contents, and run IFOLDER one more time; then run: MAKEIDX C:\TCPIP\UMAIL\MAILSTOR\xxxxxx xxxxxx where xxxxxx is your Internet login ID. (Note that it appears twice.) If you installed to a directory other than C:\TCPIP, you need to change the command above to match. WARP DISK_0 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 12-07-93 12:37p 2560 0 000000.BIO 12-07-93 12:30p 427 0 ABIOS.SYS 10-12-94 11:49a 350716 0 BUNDLE 12-07-93 12:37p 9728 0 F80000.BIO 12-07-93 12:37p 8704 0 F80100.BIO 12-07-93 12:37p 7680 0 F80200.BIO 12-07-93 12:37p 5120 0 F80402.BIO 12-07-93 12:37p 5632 0 F80403.BIO 12-07-93 12:37p 5632 0 F80404.BIO 12-07-93 12:37p 7168 0 F80600.BIO 12-07-93 12:37p 1536 0 F80700.BIO 12-07-93 12:37p 1536 0 F80701.BIO 12-07-93 12:37p 1536 0 F80702.BIO 12-07-93 12:37p 1536 0 F80703.BIO 12-07-93 12:37p 1024 0 F80704.BIO 12-07-93 12:37p 5120 0 F80902.BIO 12-07-93 12:37p 5632 0 F80903.BIO 12-07-93 12:37p 5632 0 F80904.BIO 12-07-93 12:37p 1536 0 F80A00.BIO 12-07-93 12:37p 1536 0 F80A01.BIO 12-07-93 12:37p 1024 0 F80A02.BIO 12-07-93 12:37p 5632 0 F80C00.BIO 12-07-93 12:37p 5120 0 F80D00.BIO 12-07-93 12:37p 5120 0 F80D01.BIO 12-07-93 12:37p 1536 0 F81000.BIO 12-07-93 12:37p 4096 0 F81B00.BIO 12-07-93 12:37p 2048 0 F88000.BIO 12-07-93 12:37p 11264 0 FC0400.BIO 12-07-93 12:37p 5632 0 FC0403.BIO 12-07-93 12:37p 9728 0 FC0500.BIO 10-10-94 8:22p 36376 0 LMS205.ADD 9-22-94 12:39a 1099 0 OS2BOOT 9-28-94 9:22p 12091 0 OS2DUMP 10-08-94 3:46p 555972 0 OS2KRNLI 9-30-94 2:01a 30208 0 OS2LDR 9-22-94 12:39a 8366 0 OS2LDR.MSG 12-07-93 1:02p 89 0 OS2VER 10-10-94 10:37p 40725 0 README.CID 10-10-94 9:16p 7259 0 README.INS 10-05-94 11:29p 5686 0 RESERVE.SYS 10-07-94 6:51p 75058 0 RMVIEW.EXE 9-30-94 2:03a 39472 0 SYSINSTX.COM 9-23-94 6:21a 10820 0 TEDIT.EXE 9-01-94 7:52p 14596 0 TEDIT.HLP 12-07-93 12:39p 3072 0 W020100.BIO 12-07-93 12:39p 4608 0 W020101.BIO 12-07-93 12:37p 1536 0 W050000.BIO 12-07-93 12:37p 2560 0 W050100.BIO 12-07-93 12:39p 3072 0 W050101.BIO 12-07-93 12:37p 6656 0 W060100.BIO 12-07-93 12:37p 1536 0 W0F0000.BIO 9-27-94 8:49p 1811 0 XDF.MSG 9-27-94 8:49p 89365 0 XDFCOPY.EXE WARP DISK_1 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 9-23-94 4:31a 512 0 ANSICALL.DLL 9-23-94 4:32a 512 0 BKSCALLS.DLL 9-23-94 4:34a 512 0 BMSCALLS.DLL 10-10-94 9:46p 289799 0 BUNDLE 10-09-94 8:03p 7999 0 BVHINIT.DLL 9-23-94 4:30a 512 0 BVSCALLS.DLL 9-23-94 5:17a 3735 0 CLOCK01.SYS 9-23-94 5:17a 3834 0 CLOCK02.SYS 9-23-94 5:55a 91648 0 CMD.EXE 10-10-94 8:17p 650 0 CONFIG.SYS 9-23-94 5:53a 25610 0 COUNTRY.SYS 10-10-94 5:03a 37717 0 DEL.LST 10-03-94 2:40p 3770 0 DELIVERY.SYS 9-29-94 4:26a 30 0 DISK.NUM 9-23-94 5:36a 1142 0 DOS.SYS 10-07-94 1:52p 137084 0 DOSCALL1.DLL 10-01-94 12:39p 109705 0 FDISK.COM 10-07-94 1:47p 14888 0 HARDERR.EXE 9-23-94 5:38a 135746 0 HPFS.IFS 10-05-94 11:31p 30994 0 IBM1FLPY.ADD 10-06-94 11:41p 27104 0 IBM1S506.ADD 10-05-94 11:32p 9798 0 IBM2ADSK.ADD 10-05-94 11:31p 13718 0 IBM2FLPY.ADD 10-03-94 2:39p 32373 0 IBM2SCSI.ADD 10-05-94 11:32p 9860 0 IBMINT13.I13 10-03-94 3:21p 5548 0 IBMKBD.SYS 10-03-94 3:23p 27989 0 KBDBASE.SYS 9-23-94 4:07a 1024 0 KBDCALLS.DLL 9-23-94 5:46a 5177 0 KEYBOARD.DCP 9-23-94 4:35a 1024 0 MOUCALLS.DLL 10-03-94 3:15p 17387 0 MOUSE.SYS 9-23-94 4:17a 512 0 MSG.DLL 9-23-94 4:34a 1024 0 NAMPIPES.DLL 9-23-94 4:16a 512 0 NLS.DLL 9-23-94 6:07a 25504 0 NPXEMLTR.DLL 9-23-94 4:26a 512 0 OS2CHAR.DLL 10-05-94 11:30p 33562 0 OS2DASD.DMD 10-05-94 12:05a 19358 0 OS2LOGO 10-03-94 3:38p 10910 0 PRINT01.SYS 10-03-94 3:38p 10022 0 PRINT02.SYS 9-23-94 4:19a 1024 0 QUECALLS.DLL 10-05-94 11:29p 27084 0 RESOURCE.SYS 10-08-94 8:14p 9461 0 SCREEN01.SYS 10-08-94 8:14p 9393 0 SCREEN02.SYS 10-07-94 1:54a 1536 0 SESMGR.DLL 10-08-94 2:07a 31312 0 SIPANEL1.DLL 10-08-94 2:23a 4224 0 SYSINST1.EXE 10-10-94 8:18p 143472 0 SYSINST2.EXE 9-30-94 10:43a 165 0 SYSLEVEL.OS2 9-23-94 6:21a 10820 0 TEDIT.EXE 9-01-94 7:52p 14596 0 TEDIT.HLP 10-03-94 3:38p 4970 0 TESTCFG.SYS 9-23-94 4:28a 2048 0 VIOCALLS.DLL 9-23-94 5:15a 10478 0 VTBL850.DCP 10-05-94 11:33p 14698 0 XDFLOPPY.FLT WARP DISK_1 BUNDLE ->\OS2\SRD2FIX.CMD ->\OS2\INSTALL\SHUTDOWN.EXE ->\OS2\INSTALL\BOOTDISK.EXE ->\OS2\HELP\BOOTDISK.HLP ->\OS2\INSTALL\BOOTDISK\ODPANS.DLL ->\OS2\INSTALL\BOOTDISK\ODPRTDRV.EXE ->\OS2\INSTALL\BOOTDISK\OSDELETE.EXE ->\OS2\INSTALL\BOOTDISK\OS2LDR.MSG ->\OS2\INSTALL\BOOTDISK\CONFIG.SYS ->\OS2\INSTALL\BOOTDISK\README ->\OS2\COMETRUN.EXE ->\OS2\DLL\COMETDLL.DLL ->\OS2\DLL\WPCOMET.DLL ->\OS2\BOOK\PRINTBK.INF ->\OS2\BOOK\TRADEMBK.INF ->\OS2\BOOK\MULTIMBK.INF ->\OS2\HELP\UNINSTAL.HLP ->\OS2\INSTALL\UNINSTAL.RSP ->\OS2\BOOK\WINOS2BK.INF WARP DISK_2 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 9-23-94 5:58a 49040 0 ACL.EXE 9-23-94 5:58a 23620 0 ACLCHECK.LST 9-23-94 5:59a 1520 0 ACLPANEL.DLL 9-30-94 4:49p 3362 0 BLISTLAY.OUT 10-10-94 9:49p 672745 0 BUNDLE 10-10-94 9:47p 115784 0 CDROMFLT 10-10-94 9:47p 42154 0 CDROMREQ 10-10-94 9:48p 70974 0 CGA 9-23-94 5:15a 68656 0 CHKDSK.COM 10-10-94 9:48p 94381 0 EGA 10-06-94 12:40a 68880 0 FORMAT.COM 10-08-94 2:07a 49008 0 SIPANEL2.DLL 10-08-94 2:08a 11872 0 SIPANEL3.DLL 10-08-94 2:47a 18880 0 STRTSWAP.EXE 9-23-94 6:49a 181968 0 UHPFS.DLL 9-23-94 6:24a 72048 0 UNPACK.EXE 9-23-94 6:25a 77200 0 UNPACK2.EXE 10-10-94 9:47p 218620 0 VGA WARP DISK_2 BUNDLE ->\OS2\DLL\SHPIINST.DLL ->\OS2\DLL\INSCFG32.DLL ->\OS2\DLL\DOSRFICO.DLL ->\OS2\ARCRECOV.EXE ->\OS2\INSTALL\4029OW21.EXE ->\OS2\FIND.EXE ->\OS2\DLL\COURIER.FON ->\OS2\HELP\VIEWH.HLP ->\OS2\VIOTBL.ISO ->\OS2\DLL\WPDSRVP.DLL ->\OS2\ARCINST.EXE ->\OS2\DLL\WPDSERV.DLL ->\OS2\DLL\SOMS.DLL ->\OS2\VIOTBL.DCP ->\OS2\WPDSACTV.EXE ->\OS2\BOOT\VIOTBL.DCP ->\OS2\HELP\HMHELP.HLP ->\OS2\SOMDD.EXE ->\OS2\DLL\MISC.FON ->\OS2\SOMDSVR.EXE ->\OS2\BOOT\RESOURCE.SYS ->\OS2\DLL\PMTKT.DLL ->\OS2\VIEW.EXE ->\OS2\BOOT\OS2CDROM.DMD ->\OS2\DLL\SYSMONO.FON ->\OS2\DLL\WPCONMRI.DLL ->\OS2\VIEWDOC.EXE ->\OS2\BLDLEVEL.EXE ->\OS2\HELP\DSPINSTL.HLP ->\OS2\SETBOOT.EXE ->\OS2\INSTALL\PARSEDB.EXE ->\OS2\CONVERT.EXE ->\OS2\DLL\ANMT.DLL ->\OS2\DLL\BVHMPA.DLL ->\OS2\MONITOR.DIF ->\OS2\ETC\WPDSERV.IR ->\OS2\DLL\BVHWNDW.DLL ->\OS2\DLL\SYSFONT.DLL ->\OS2\CLIPOS2.EXE ->\OS2\DLL\HPMGRMRI.DLL ->\OS2\DLL\SERIAL.PDR ->\OS2\PMFORMAT.EXE ->\OS2\DLL\WINCFG.DLL ->\OS2\HELP\MIGRATE.HLP ->\OS2\KEYBOARD.DCP ->\OS2\DLL\PMPRINT.QPR ->\OS2\KEYB.COM ->\OS2\DLL\FKA.DLL ->\OS2\DLL\PARALLEL.PDR ->\OS2\WIN_30.RC ->\OS2\INSTALL\CDROM.TBL ->\OS2\INSTALL\SCSI.TBL ->\OS2\INSTALL\PCMCIA.TBL WARP DISK_3 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-10-94 9:51p 1279901 0 BUNDLE 10-10-94 9:50p 287420 0 DOS 10-10-94 9:49p 33003 0 PRESCHEK 10-10-94 9:49p 189112 0 SCSIADDS 10-10-94 9:49p 33201 0 XVAVESA WARP DISK_3 BUNDLE ->\OS2\ETC\WPSH.IR ->\OS2\DLL\PMVIOP.DLL ->\OS2\INSTALL\DATABASE.TXT ->\OS2\DLL\PMPRE.DLL ->\OS2\DLL\DISPLAY.DLL ->\OS2\DLL\PMVDMP.DLL ->\OS2\DLL\PMDCTLS.DLL ->\OS2\E.EXE ->\OS2\RMVIEW.EXE ->\OS2\MODE.COM ->\OS2\DLL\SOMEM.DLL ->\OS2\MAKEINI.EXE ->\OS2\XCOPY.EXE ->\OS2\DLL\VIDEOCFG.DLL ->\OS2\HELP\INSTALL.HLP ->\OS2\DLL\INSPGM32.DLL ->\OS2\DLL\IBMGPMI.DLL ->\OS2\DISKCOPY.COM ->\OS2\HELP\WPMSG.HLP ->\OS2\SYSLEVEL.EXE ->\OS2\DLL\PMSHLTKT.DLL ->\OS2\BOOT.COM ->\OS2\DLL\SVGAINST.DLL ->\OS2\DLL\PMBIND.DLL ->\OS2\DISKCOMP.COM ->\OS2\DLL\SVGA.DLL ->\OS2\DLL\PMPIC.DLL ->\OS2\DLL\BDCALLS.DLL ->\OS2\UNDELETE.COM ->\OS2\REPLACE.EXE ->\OS2\INSTALL\DDINSTAL.EXE ->\OS2\HELP\ICONEDIT.HLP ->\OS2\EAUTIL.EXE ->\OS2\COMP.COM ->\OS2\DLL\CDTBL.DLL ->\OS2\HELPMSG.EXE ->\OS2\DLL\MMSNIFF.DLL ->\OS2\MORE.COM ->\OS2\DLL\SEAMLESS.DLL ->\OS2\PRINT.COM ->\OS2\PMCHKDSK.EXE ->\OS2\DLL\MINXOBJ.DLL ->\OS2\HELP\EHXHP.HLP ->\OS2\DLL\WPPRTMRI.DLL ->\OS2\DLL\SOMTC.DLL ->\OS2\WPDSINIT.EXE ->\OS2\BOOT\OS2DASD.DMD ->\OS2\DLL\PMVDMH.DLL WARP DISK_4 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-10-94 9:54p 1427512 0 BUNDLE 10-10-94 9:51p 172875 0 REXX 9-26-94 9:45p 5306 0 VGA.DSP 10-10-94 9:52p 247533 0 VGABUN WARP DISK_4 BUNDLE ->\OS2\DLL\PMSPL.DLL ->\OS2\HELP\GLOSS\WPGLOSS.HLP ->\OS2\DLL\PMATM.DLL ->\OS2\ETC\SOM.IR ->\OS2\DLL\OASIS.DLL ->\OS2\ICONEDIT.EXE ->\OS2\DLL\HELV.FON ->\OS2\INSTALL\DSPINSTL.EXE ->\OS2\SYSTEM\OSO001H.MSG ->\OS2\DLL\SOM.DLL ->\OS2\DLL\SOMIR.DLL ->\OS2\INSTALL\RSPDSPI.EXE ->\PSFONTS\COURB.PFB ->\PSFONTS\COUR.PFB ->\PSFONTS\COURBI.PFB ->\PSFONTS\COURI.PFB ->\OS2\DLL\SOMU.DLL ->\OS2\DLL\IBMNULL\IBMNULL.DRV ->\PSFONTS\SYMB.PFB ->\OS2\SYSTEM\OSO001.MSG ->\OS2\DLL\PMWPMRI.DLL ->\OS2\BOOT\REFPART.SYS WARP DISK_5 BUNDLE ->\OS2\DLL\PMMERGE.DLL ->\OS2\DLL\PMWP.DLL ->\OS2\HELP\WPHELP.HLP WARP DISK_6 BUNDLE ->\OS2\DLL\PMCTLS.DLL ->\OS2\DLL\MIRRORS.DLL ->\OS2\DLL\WPCONFIG.DLL ->\OS2\INSTALL\INSTALL.EXE ->\OS2\DLL\WPPRINT.DLL ->\OS2\DLL\SOMD.DLL ->\OS2\DLL\OS2MM.DLL ->\OS2\DLL\PMGPI.DLL ->\OS2\DLL\HELPMGR.DLL ->\OS2\INSTALL\MIGRATE.EXE ->\README WARP DISK_7 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-12-94 11:34a 3570 0 APMDELL 10-12-94 11:34a 81617 0 CID 10-12-94 11:32a 11114 0 COURPSF 10-12-94 11:33a 129165 0 EPM 10-12-94 11:34a 120186 0 FDISK 10-12-94 11:32a 56908 0 HELVB.PFB 10-12-94 11:34a 514275 0 PACK0 10-12-94 11:32a 70491 0 PACK11 10-12-94 11:32a 12736 0 PACK12 10-12-94 11:32a 60462 0 PACK13 10-12-94 11:32a 27342 0 PACK14 10-12-94 11:32a 16219 0 PACK15 10-12-94 11:33a 143511 0 PACK17 10-12-94 11:32a 17096 0 PACK32 10-12-94 11:32a 34851 0 PMREXX 10-12-94 11:34a 171559 0 REQUIRED 10-12-94 11:32a 20323 0 RESTORE 10-12-94 11:33a 31756 0 RIPLINST 10-12-94 11:32a 24214 0 SYSMONO.BMP 10-12-94 11:33a 206728 0 TIMES.BMP 10-12-94 11:32a 61019 0 TNR.PFB WARP DISK_7 PACK0 ->\MMTEMP\OS20PROC.DLL ->\MMTEMP\SSMRES.DLL ->\MMTEMP\BELLS.WAV ->\MMTEMP\MEMSH.DLL ->\MMTEMP\SSMDD.SYS ->\MMTEMP\CUCKOO.WAV ->\MMTEMP\SHRED.WAV ->\MMTEMP\STPMH.HLP ->\MMTEMP\RDIBPROC.DLL ->\MMTEMP\AUTOPROC.DLL ->\MMTEMP\WI30PROC.DLL ->\MMTEMP\BOO.WAV ->\MMTEMP\BUSAUDIO.SYS ->\MMTEMP\FFC.HLP ->\MMTEMP\IMAADPCM.DLL ->\MMTEMP\SSSH.DLL ->\MMTEMP\WM_TELL.WAV ->\MMTEMP\TAKEMY.WAV ->\MMTEMP\BALLGAME.MID ->\MMTEMP\ADSHDD.SYS ->\MMTEMP\HOLIDAY.MID ->\MMTEMP\MMEINDEX.HLP ->\MMTEMP\AMPM.EXE ->\MMTEMP\DOORCLS.WAV ->\MMTEMP\LASER.WAV ->\MMTEMP\DRWCLOSE.WAV ->\MMTEMP\BLUEJAM.MID ->\MMTEMP\IBMLANLK.EXE ->\MMTEMP\DRUMROLL.WAV ->\MMTEMP\AVCIIOPR.DLL ->\MMTEMP\MMOTPROC.DLL ->\MMTEMP\MMMRI.DLL ->\MMTEMP\EEEOOOP.WAV ->\MMTEMP\BBEE.MID ->\MMTEMP\STPMMRI.DLL ->\MMTEMP\MDM.DLL ->\MMTEMP\MDMI.DLL ->\MMTEMP\BWEEEP.WAV ->\MMTEMP\BEEOONG.WAV ->\MMTEMP\MPPM.EXE ->\MMTEMP\AMPMH.HLP ->\MMTEMP\SNDBLAST.DLL ->\MMTEMP\MCIMRI.DLL ->\MMTEMP\OS13PROC.DLL ->\MMTEMP\BWAAANG.WAV ->\MMTEMP\BACH.MID ->\MMTEMP\IBMRALLY.MID ->\MMTEMP\CARDINFO.DLL ->\MMTEMP\EEERRUPP.WAV ->\MMTEMP\DOINK.WAV ->\MMTEMP\MCIREC.HLP ->\MMTEMP\MCIERR.DLL ->\MMTEMP\MMSNDH.HLP ->\MMTEMP\FFCMRI.DLL ->\MMTEMP\WEPMMRI.DLL ->\MMTEMP\MIPM.DLL ->\MMTEMP\NULLSH.DLL ->\MMTEMP\R0STUB.SYS ->\MMTEMP\BOING.WAV ->\MMTEMP\MPPMMRI.DLL ->\MMTEMP\MASTERH9.RT ->\MMTEMP\PLAY.CMD ->\MMTEMP\QRYADH.HLP ->\MMTEMP\FOURMEG.SCR ->\MMTEMP\IBMLANLK.SYS ->\MMTEMP\AUDIOVDD.SYS ->\MMTEMP\MPPM.EAS ->\MMTEMP\BUSAUDIO.HLP ->\MMTEMP\SOUNDS.EAS ->\MMTEMP\IOPRNLS.DLL ->\MMTEMP\CONTROL.SCR ->\MMTEMP\RECORD.CMD ->\MMTEMP\MIDIFILE.ICO ->\MMTEMP\DATACONV.ICO ->\MMTEMP\AUDFILE.ICO ->\MMTEMP\MMPMDATA.ICO ->\MMTEMP\MMPMINST.ICO ->\MMTEMP\MMPMFLD2.ICO ->\MMTEMP\VOLCTRL.ICO ->\MMTEMP\MMSETUP.ICO ->\MMTEMP\MMPMFLDR.ICO ->\MMTEMP\MIDIPLAY.ICO ->\MMTEMP\AUDREC.ICO ->\MMTEMP\VIDPLAY.ICO ->\MMTEMP\VDSCPLAY.ICO ->\MMTEMP\CDPLAYER.ICO ->\MMTEMP\AUDPLAY.ICO ->\MMTEMP\WEPM.EAS ->\MMTEMP\MINSTALL.EAS ->\MMTEMP\STDLH.HLP ->\MMTEMP\AMPMMRI.DLL ->\MMTEMP\MOVIES.EAS ->\MMTEMP\GENINMRI.DLL ->\MMTEMP\MIDIICO.EAS ->\MMTEMP\WAVEICO.EAS ->\MMTEMP\MMIO.DLL ->\MMTEMP\MMIOI.DLL ->\MMTEMP\VAUDIO.SYS ->\MMTEMP\MPMCDIMG.CMD ->\MMTEMP\TWIP.WAV ->\MMTEMP\POP.WAV ->\MMTEMP\SOUNDS.ICO ->\MMTEMP\MOVIE.ICO ->\MMTEMP\AVSFILM.ICO ->\MMTEMP\FILMFLDR.ICO ->\MMTEMP\STDLMRI.DLL ->\MMTEMP\QRYCDMRI.DLL ->\MMTEMP\QRYADMRI.DLL ->\MMTEMP\SSM.DLL ->\MMTEMP\LSIH.MSG ->\MMTEMP\MMSNDMRI.DLL ->\MMTEMP\SYSLEVEL.MPM ->\MMTEMP\DINSTSND.CMD ->\MMTEMP\INSTSND.CMD ->\MMTEMP\BSAUDRES.DLL ->\MMTEMP\FSSH.DLL ->\MMTEMP\AVIO.DLL ->\MMTEMP\MIDIIO.DLL ->\MMTEMP\WAVEPROC.DLL ->\MMTEMP\MISH.DLL ->\MMTEMP\MIDIMCD.DLL ->\MMTEMP\AUDIOMCD.DLL ->\MMTEMP\AMPMXMCD.DLL ->\MMTEMP\AUDIOIF.DLL ->\MMTEMP\HHP.DLL ->\MMTEMP\AUDIOSH.DLL ->\MMTEMP\LSI.MSG ->\MMTEMP\WAVEFILE.EAS ->\MMTEMP\BASECONF.CH ->\MMTEMP\MME.MSG ->\MMTEMP\AUDIODD.MSG WARP DISK_7 PACK11 ->\MMTEMP\OS2\DRIVERS\CS4231\CS31BA11.DRV ->\MMTEMP\OS2\DRIVERS\CS4231\VSNDSYS.386 ->\MMOS2\CS4231.SYS ->\MMOS2\VCS4231.SYS ->\MMTEMP\OS2\DRIVERS\CS4231\CS31BA11.INI ->\MMTEMP\OS2\DRIVERS\CS4231\TP750INI.ADD WARP DISK_7 PACK12 ->\MMOS2\BUSAUDIO.SYS ->\MMOS2\HELP\BUSAUDIO.HLP ->\MMOS2\DLL\BSAUDRES.DLL WARP DISK_7 PACK13 ->\MMOS2\DLL\MPGIO.DLL ->\MMOS2\VIDRMS.SYS ->\MMOS2\RMAUDIO.SYS ->\MMOS2\DSP\VREEL.BIN ->\MMOS2\DSP\DSP.BIN ->\MMOS2\DLL\MPGDC.DLL ->\MMOS2\VIDRMS1.INI WARP DISK_7 PACK14 ->\MMOS2\DLL\WEPMPINT.DLL ->\MMOS2\DLL\WEPMPLUS.DLL ->\MMOS2\HELP\WEPMPLUS.HLP WARP DISK_7 PACK15 ->\MMOS2\BUSAUDIO.SYS ->\MMOS2\DSP\DSPLITE.BIN ->\MMOS2\HELP\BUSAUDIO.HLP ->\MMOS2\DLL\BSAUDRES.DLL WARP DISK_7 PACK17 ->\MMOS2\MVPRODD.SYS ->\MMTEMP\OS2\DRIVERS\MVPRODD\PROMIX.EXE ->\MMTEMP\OS2\DRIVERS\MVPRODD\OPL3.DRV ->\MMTEMP\OS2\DRIVERS\MVPRODD\MVMIXER.DRV ->\MMTEMP\OS2\DRIVERS\MVPRODD\MVPROAUD.DRV ->\MMTEMP\OS2\DRIVERS\MVPRODD\MVSOUND.SYS ->\MMTEMP\OS2\DRIVERS\MVPRODD\SBWAVE.DRV ->\MMTEMP\OS2\DRIVERS\MVPRODD\MVFM.DRV ->\MMTEMP\OS2\DRIVERS\MVPRODD\MVFM.DRV ->\MMTEMP\OS2\DRIVERS\MVPRODD\VPASD.386 ->\MMTEMP\OS2\DRIVERS\MVPRODD\MMMIXER.DLL ->\MMTEMP\OS2\DRIVERS\MVPRODD\MCIMIXER.DRV ->\MMTEMP\OS2\DRIVERS\MVPRODD\MIDIMAP.CFG ->\MMOS2\HELP\PAS16.HLP ->\MMTEMP\OS2\DRIVERS\MVPRODD\VADMAD.386 ->\MMTEMP\OS2\DRIVERS\MVPRODD\OEMSETUP.INF ->\MMTEMP\OS2\DRIVERS\MVPRODD\MV.INI WARP DISK_7 PACK32 ->\MMOS2\VIDVBC.SYS ->\MMOS2\HELP\VIDBLAST.HLP ->\MMOS2\VIDVBC1.INI WARP DISK_8 PACK0 ->\MMTEMP\MMPM.DLL ->\MMTEMP\MMPMINI.DLL ->\MMTEMP\MACAW.AVI ->\MMTEMP\MINSTALL.EXE ->\MMTEMP\PCDIO.DLL ->\MMTEMP\WEPM.EXE ->\MMTEMP\MMSND.DLL ->\MMTEMP\GENIN.DLL ->\MMTEMP\MMPMCRTS.DLL ->\MMTEMP\SW.DLL ->\MMTEMP\SND.DLL ->\MMTEMP\DIVE.DLL ->\MMTEMP\STARTUP.WAV ->\MMTEMP\JET.WAV ->\MMTEMP\MPPM.DLL ->\MMTEMP\AUDIO.XLM ->\MMTEMP\QRYAD.DLL ->\MMTEMP\STPM.EXE ->\MMTEMP\QRYCD.DLL ->\MMTEMP\WEPMH.HLP ->\MMTEMP\MCIAPI.DLL ->\MMTEMP\MIPMINI.DLL ->\MMTEMP\IMGCLASS.DLL ->\MMTEMP\IOBASE.DLL ->\MMTEMP\ITERM.DLL ->\MMTEMP\FFC.EXE ->\MMTEMP\AUDIO2.WG2 ->\MMTEMP\AUDIO.WG2 ->\MMTEMP\MMINSTH.HLP ->\MMTEMP\MCIREXX.INF ->\MMTEMP\SHUTDOWN.WAV ->\MMTEMP\MPPMH.HLP ->\MMTEMP\STDL.DLL ->\MMTEMP\AVCAPROC.DLL ->\MMTEMP\SSMINI.DLL ->\MMTEMP\WOOEEP.WAV WARP DISK_9 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-10-94 10:05p 17625 0 BACKUP 10-10-94 10:03p 10050 0 BITMAP 10-10-94 10:04p 61570 0 COURBI.PFB 10-10-94 10:03p 159336 0 EPM 10-10-94 10:04p 210219 0 HELV.BMP 10-10-94 10:04p 57440 0 HELVI.PFB 10-10-94 10:03p 106218 0 PACK18 10-10-94 10:05p 44535 0 PACK20 10-10-94 10:05p 17096 0 PACK31 10-10-94 10:03p 815461 0 PACK36 10-10-94 10:04p 152897 0 PACK44 10-10-94 10:05p 12736 0 PACK8 10-10-94 10:05p 23222 0 PULSE 10-10-94 10:04p 64847 0 TNRBI.PFB 10-10-94 10:05p 11768 0 VDPMI 10-10-94 10:04p 71961 0 WINBASE 18 file(s) 1836981 bytes used 0 bytes free WARP DISK_9 PACK18 ->\MMOS2\JAZZDD.SYS ->\MMTEMP\OS2\DRIVERS\JAZZDD\JAZZMXD.DRV ->\MMTEMP\OS2\DRIVERS\JAZZDD\JAZZFM4.DRV ->\MMTEMP\OS2\DRIVERS\JAZZDD\JAZZ.DRV ->\MMTEMP\OS2\DRIVERS\JAZZDD\JAZZFM2.DRV ->\MMTEMP\OS2\DRIVERS\JAZZDD\MCICDA.DRV ->\MMTEMP\OS2\DRIVERS\JAZZDD\JAZZ401.DRV ->\MMTEMP\OS2\DRIVERS\JAZZDD\MMMIXER.DLL ->\MMTEMP\OS2\DRIVERS\JAZZDD\JAZZ.SYS ->\MMTEMP\OS2\DRIVERS\JAZZDD\MIDIMAP.CFG ->\MMOS2\HELP\JAZZ16.HLP ->\MMTEMP\OS2\DRIVERS\JAZZDD\VJAZZD.386 ->\MMTEMP\OS2\DRIVERS\JAZZDD\VJAZZFM.386 ->\MMTEMP\OS2\DRIVERS\JAZZDD\OEMSETUP.INF WARP DISK_9 PACK20 ->\MMOS2\DLL\SMVSPAGE.DLL ->\MMOS2\HELP\SMVSH.HLP ->\MMOS2\DLL\SMVSMRI.DLL ->\MMTEMP\VAPM.SCR WARP DISK_9 PACK31 ->\MMOS2\VIDVBC.SYS ->\MMOS2\HELP\VIDBLAST.HLP ->\MMOS2\VIDVBC1.INI WARP DISK_9 PACK36 ->\MMTEMP\OS2\DRIVERS\SBAWED2\SYNTHGS.SBK ->\MMTEMP\OS2\DRIVERS\SBAWED2\AWEGUI.DLL ->\MMTEMP\OS2\DRIVERS\SBAWED2\SYNTHMT.SBK ->\MMOS2\SBAWED2.SYS ->\MMTEMP\OS2\DRIVERS\SBAWED2\SBAWE32.DRV ->\MMTEMP\OS2\DRIVERS\SBAWED2\AWEMAN.DLL ->\MMTEMP\OS2\DRIVERS\SBAWED2\SB16SND.DRV ->\MMTEMP\OS2\DRIVERS\SBAWED2\SB16AUX.DRV ->\MMTEMP\OS2\DRIVERS\SBAWED2\SYNTHGM.SBK ->\MMTEMP\OS2\DRIVERS\SBAWED2\CSPMAN.DLL ->\MMTEMP\OS2\DRIVERS\SBAWED2\WFM0011.ACV ->\MMTEMP\OS2\DRIVERS\SBAWED2\SBPFM.DRV ->\MMTEMP\OS2\DRIVERS\SBAWED2\WFM0007.ACV ->\MMTEMP\OS2\DRIVERS\SBAWED2\WFM0200.ACV ->\MMTEMP\OS2\DRIVERS\SBAWED2\WFM0006.ACV ->\MMTEMP\OS2\DRIVERS\SBAWED2\WFM0203.ACV ->\MMTEMP\OS2\DRIVERS\SBAWED2\WFM0202.ACV ->\MMOS2\HELP\SBLASTER.HLP ->\MMTEMP\OS2\DRIVERS\SBAWED2\VSBPD.386 ->\MMOS2\DSP\WI0200.ASP ->\MMOS2\DSP\WO0200.ASP ->\MMTEMP\OS2\DRIVERS\SBAWED2\MIDIMAP.CFG ->\MMOS2\DSP\WI0007.ASP ->\MMOS2\DSP\WI0006.ASP ->\MMOS2\DSP\WO0007.ASP ->\MMOS2\DSP\WO0006.ASP ->\MMTEMP\OS2\DRIVERS\SBAWED2\SBWIN.INI ->\MMTEMP\OS2\DRIVERS\SBAWED2\OEMSETUP.INF WARP DISK_9 PACK44 ->\MMOS2\ACPADD2.SYS ->\MMTEMP\OS2\DRIVERS\ACPADD2\AUDIO.DLL ->\MMTEMP\OS2\DRIVERS\ACPADD2\ACPADD.SYS ->\MMTEMP\OS2\DRIVERS\ACPADD2\ACPA.DRV ->\MMTEMP\OS2\DRIVERS\ACPADD2\AUDIOVER.EXE ->\MMTEMP\OS2\DRIVERS\ACPADD2\IBMMPC.DSP ->\MMTEMP\OS2\DRIVERS\ACPADD2\IBMAUDS.DSP ->\MMOS2\DSP\IBMPCMR8.DSP ->\MMOS2\DSP\IBMAUDS.DSP ->\MMOS2\DSP\IBMMPC.DSP ->\MMTEMP\OS2\DRIVERS\ACPADD2\IBMPCMR.DSP ->\MMOS2\DSP\IBMPCMR.DSP ->\MMTEMP\OS2\DRIVERS\ACPADD2\IBMPCMP.DSP ->\MMTEMP\OS2\DRIVERS\ACPADD2\MIDIMAP.CFG ->\MMOS2\DSP\IBMXA.DSP ->\MMOS2\DSP\IBMPMM48.DSP ->\MMOS2\DSP\IBMPCMP.DSP ->\MMOS2\DSP\IBMAUDR.DSP ->\MMOS2\DSP\IBMAUDP.DSP ->\MMOS2\DSP\IBMAUDG.DSP ->\MMOS2\DSP\IBMAUDF.DSP ->\MMTEMP\OS2\DRIVERS\ACPADD2\OEMSETUP.INF WARP DISK_9 PACK8 ->\MMOS2\BUSAUDIO.SYS ->\MMOS2\HELP\BUSAUDIO.HLP ->\MMOS2\DLL\BSAUDRES.DLL WARP DISK_10 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-10-94 10:06p 159 0 ATMFONTS.QLC 10-10-94 10:07p 51476 0 BIDI 10-10-94 10:06p 171884 0 BITMAP 10-10-94 10:07p 280557 0 CMDREF 10-10-94 10:07p 60712 0 COURIER.BMP 10-10-94 10:07p 172652 0 HPFS 10-10-94 10:06p 324045 0 MAHJONGG 10-10-94 10:06p 10808 0 MOUSE 10-10-94 10:05p 328890 0 PACK2 10-10-94 10:07p 17096 0 PACK22 10-10-94 10:07p 14081 0 PACK28 10-10-94 10:07p 64510 0 PACK34 10-10-94 10:07p 12736 0 PACK9 10-10-94 10:07p 88194 0 PCMCIADD 9-26-94 9:45p 49 0 PEN.DAT 10-10-94 10:07p 48091 0 PICVIEW 10-10-94 10:07p 29812 0 RECOVER 10-10-94 10:07p 126336 0 REXXPUBS 10-10-94 10:07p 21025 0 TREE WARP DISK_10 PACK2 ->\MMOS2\DLL\INDFSR31.DLL ->\MMOS2\DLL\INDEO.DLL ->\MMOS2\DLL\INDRTR31.DLL ->\MMOS2\DLL\INDDEC32.DLL ->\MMOS2\DLL\LVDP8000.DLL ->\MMOS2\RGBTOYUV.LUT ->\MMOS2\DLL\VIDVCI.DLL ->\MMOS2\DLL\ULCOASYM.DLL ->\MMOS2\DLL\ULDC.DLL ->\MMOS2\DLL\MONDO.DLL ->\MMOS2\VCSHDD.SYS ->\MMOS2\DLL\ULCORT.DLL ->\MMOS2\DLL\CODECSH.DLL ->\MMOS2\DLL\SVMCMRI.DLL ->\MMTEMP\SMVINI.SCR ->\MMOS2\HELP\SVMCH.HLP ->\MMTEMP\VIDICON.EAS ->\MMOS2\DLL\MTSH.DLL ->\MMOS2\DLL\SVMC.DLL ->\MMOS2\DLL\SVSH.DLL ->\MMOS2\DLL\ULDC16.DLL ->\MMOS2\DLL\ULDC8.DLL ->\MMOS2\DLL\INDEOR31.DLL ->\MMTEMP\SMVCONF.CH WARP DISK_10 PACK22 ->\MMOS2\VIDVBC.SYS ->\MMOS2\HELP\VIDBLAST.HLP ->\MMOS2\VIDVBC1.INI WARP DISK_10 PACK28 ->\MMOS2\VIDVBC.SYS ->\MMOS2\HELP\VIDMAGIC.HLP ->\MMOS2\VIDVBC1.INI WARP DISK_10PACK34 ->\MMTEMP\OS2\DRIVERS\AZT16DD\MM16C.DRV ->\MMOS2\AZT16DD.SYS ->\MMOS2\SGAUDVDD.SYS ->\MMTEMP\OS2\DRIVERS\AZT16DD\OEMSETUP.INF ->\MMTEMP\OS2\DRIVERS\AZT16DD\MIDIMAP.CFG WARP DISK_10 PACK9 ->\MMOS2\BUSAUDIO.SYS ->\MMOS2\HELP\BUSAUDIO.HLP ->\MMOS2\DLL\BSAUDRES.DLL WARP DISK_11 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-10-94 10:10p 25352 0 APM 10-10-94 10:10p 135681 0 BITMAP 10-10-94 10:08p 122605 0 CHESS 10-10-94 10:08p 58808 0 HELVBI.PFB 10-10-94 10:08p 162230 0 KLONDIKE 10-10-94 10:09p 264303 0 LINK 10-10-94 10:10p 15375 0 PACK16 10-10-94 10:08p 75947 0 PACK35 10-10-94 10:10p 21127 0 RAS 10-10-94 10:08p 19815 0 SORT 10-10-94 10:08p 47362 0 SYMB.PFB 10-10-94 10:08p 13231 0 TIMESPSF 10-10-94 10:08p 61713 0 TNRB.PFB 10-10-94 10:08p 64819 0 TNRI.PFB 10-10-94 10:09p 737258 0 TUTORIAL 10-10-94 10:08p 11169 0 VEMM 18 file(s) 1836795 bytes used 0 bytes free WARP DISK_11 PACK16 ->\MMOS2\VIDVBC.SYS ->\MMOS2\VIDVBC1.INI ->\MMOS2\REGION\CCIRCATV.RGN ->\MMOS2\REGION\JAPAN.RGN ->\MMOS2\REGION\JPNCATV.RGN ->\MMOS2\REGION\AUS.RGN ->\MMOS2\REGION\USA.RGN ->\MMOS2\REGION\CCIR.RGN ->\MMOS2\REGION\USACATV.RGN WARP DISK_11 PACK35 ->\MMTEMP\OS2\DRIVERS\ES688DD\ES688WIN.DRV ->\MMOS2\ES688DD.SYS ->\MMTEMP\OS2\DRIVERS\ES688DD\MSMIXMGR.DLL ->\MMTEMP\OS2\DRIVERS\ES688DD\ES688WIN.386 ->\MMTEMP\OS2\DRIVERS\ES688DD\AUDMPIO.DRV ->\MMTEMP\OS2\DRIVERS\ES688DD\MIDIMAP.CFG ->\MMOS2\HELP\ES688INS.HLP ->\MMOS2\DLL\ESSVSD88.DLL WARP DISK_12 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-10-94 10:10p 22682 0 ATTRIB 10-10-94 10:10p 62417 0 COURB.PFB 10-10-94 10:10p 60187 0 COURI.PFB 10-10-94 10:12p 595963 0 DOS 10-10-94 10:11p 191210 0 INSTAID 10-10-94 10:10p 12736 0 PACK10 10-10-94 10:10p 14095 0 PACK29 10-10-94 10:10p 17096 0 PACK33 10-10-94 10:10p 48441 0 PACK40 10-10-94 10:11p 64082 0 PACK41 10-10-94 10:12p 358 0 PACK43 10-10-94 10:11p 93711 0 PACK5 10-10-94 10:11p 127956 0 PCMCIA 10-10-94 10:10p 31609 0 PMSEEK 10-10-94 10:12p 166821 0 RAS 10-10-94 10:12p 5171 0 VXMS 10-10-94 10:11p 310911 0 WINENV 10-10-94 10:10p 8525 0 WINTOUCH 20 file(s) 1833971 bytes used 0 bytes free WARP DISK_12 PACK10 ->\MMOS2\BUSAUDIO.SYS ->\MMOS2\HELP\BUSAUDIO.HLP ->\MMOS2\DLL\BSAUDRES.DLL WARP DISK_12 PACK29 ->\MMOS2\VIDVBC.SYS ->\MMOS2\HELP\VIDWINDW.HLP ->\MMOS2\VIDVBC1.INI WARP DISK_12 PACK33 ->\MMOS2\VIDVBC.SYS ->\MMOS2\HELP\VIDBLAST.HLP ->\MMOS2\VIDVBC1.INI WARP DISK_12 PACK40 ->\MMOS2\SBD2.SYS ->\MMTEMP\OS2\DRIVERS\SBD2\SB20SND.DRV ->\MMTEMP\OS2\DRIVERS\SBD2\SBFM.DRV ->\MMOS2\HELP\SBLASTER.HLP ->\MMTEMP\OS2\DRIVERS\SBD2\MIDIMAP.CFG ->\MMTEMP\OS2\DRIVERS\SBD2\VSBPD.386 ->\MMTEMP\OS2\DRIVERS\SBD2\OEMSETUP.INF WARP DISK_12 PACK41 ->\MMOS2\SBPD2.SYS ->\MMTEMP\OS2\DRIVERS\SBPD2\SBPAUX.DRV ->\MMTEMP\OS2\DRIVERS\SBPD2\SBPSND.DRV ->\MMTEMP\OS2\DRIVERS\SBPD2\SBPFM.DRV ->\MMOS2\HELP\SBLASTER.HLP ->\MMTEMP\OS2\DRIVERS\SBPD2\MIDIMAP.CFG ->\MMTEMP\OS2\DRIVERS\SBPD2\VSBPD.386 ->\MMTEMP\OS2\DRIVERS\SBPD2\OEMSETUP.INF WARP DISK_12 PACK43 ->\MMTEMP\OS2\DRIVERS\SB16D2\OEMSETUP.INF WARP DISK_12 PACK5 ->\MMOS2\CDPM.EXE ->\MMOS2\DLL\CDTBL.DLL ->\MMOS2\DLL\IBMCDXA.DLL ->\MMOS2\HELP\CDPMH.HLP ->\MMOS2\DLL\CDPMMRI.DLL ->\MMOS2\INSTALL\CDPM.EAS ->\MMOS2\DLL\CDDASH.DLL ->\MMOS2\DLL\GENCDVSD.DLL ->\MMOS2\DLL\CDAUDIO.DLL WARP DISK_13 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-10-94 10:13p 59084 0 AUDIOWIN 10-10-94 10:13p 62046 0 COUR.PFB 10-10-94 10:12p 255100 0 EPM 10-10-94 10:13p 54946 0 HELV.PFB 10-10-94 10:13p 12725 0 HELVPSF 10-10-94 10:13p 20450 0 LABEL 10-10-94 10:13p 32444 0 PACK30 10-10-94 10:13p 65383 0 PACK42 10-10-94 10:13p 128775 0 PACK43 10-10-94 10:12p 7147 0 RAS 10-10-94 10:13p 11247 0 SERIAL 10-10-94 10:13p 102879 0 TOUCH 14 file(s) 812226 bytes used 0 bytes free WARP DISK_13 PACK30 ->\MMOS2\SBD2.SYS ->\MMOS2\RMAUDIO.SYS ->\MMTEMP\RMSBLAST.SCR WARP DISK_13 PACK42 ->\MMOS2\SBP2D2.SYS ->\MMTEMP\OS2\DRIVERS\SBP2D2\SBPAUX.DRV ->\MMTEMP\OS2\DRIVERS\SBP2D2\SBPSND.DRV ->\MMTEMP\OS2\DRIVERS\SBP2D2\SBPFM.DRV ->\MMOS2\HELP\SBLASTER.HLP ->\MMTEMP\OS2\DRIVERS\SBP2D2\MIDIMAP.CFG ->\MMTEMP\OS2\DRIVERS\SBP2D2\VSBPD.386 ->\MMTEMP\OS2\DRIVERS\SBP2D2\OEMSETUP.INF WARP DISK_13 PACK43 ->\MMOS2\SB16D2.SYS ->\MMTEMP\OS2\DRIVERS\SB16D2\SB16SND.DRV ->\MMTEMP\OS2\DRIVERS\SB16D2\SB16AUX.DRV ->\MMTEMP\OS2\DRIVERS\SB16D2\CSPMAN.DLL ->\MMTEMP\OS2\DRIVERS\SB16D2\WFM0011.ACV ->\MMTEMP\OS2\DRIVERS\SB16D2\SBPFM.DRV ->\MMTEMP\OS2\DRIVERS\SB16D2\WFM0007.ACV ->\MMTEMP\OS2\DRIVERS\SB16D2\WFM0200.ACV ->\MMTEMP\OS2\DRIVERS\SB16D2\WFM0006.ACV ->\MMTEMP\OS2\DRIVERS\SB16D2\WFM0203.ACV ->\MMTEMP\OS2\DRIVERS\SB16D2\WFM0202.ACV ->\MMOS2\HELP\SBLASTER.HLP ->\MMTEMP\OS2\DRIVERS\SB16D2\MIDIMAP.CFG ->\MMTEMP\OS2\DRIVERS\SB16D2\VSBPD.386 ->\MMOS2\DSP\WI0200.ASP ->\MMOS2\DSP\WO0200.ASP ->\MMOS2\DSP\WI0007.ASP ->\MMOS2\DSP\WO0007.ASP ->\MMOS2\DSP\WI0006.ASP ->\MMOS2\DSP\WO0006.ASP WARP DISPLAY DISK_1 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-10-94 10:21p 159449 0 8514 9-26-94 9:44p 956 0 AT480AC.DSP 9-26-94 9:44p 954 0 AT480BC.DSP 9-26-94 9:44p 963 0 AT600BC.DSP 9-26-94 9:44p 1129 0 AT768BC.DSP 9-26-94 9:45p 279 0 ATIM32A.DSP 9-26-94 9:45p 279 0 ATIM64A.DSP 10-09-94 8:09p 10251 0 BVHMPA.DL_ 9-26-94 9:44p 970 0 CL480AC.DSP 9-26-94 9:44p 967 0 CL480BC.DSP 9-26-94 9:45p 277 0 CL54XA.DSP 9-26-94 9:44p 976 0 CL600BC.DSP 9-26-94 9:44p 1141 0 CL768BC.DSP 10-10-94 10:19p 4 0 DISK.NUM 9-23-94 4:32a 38288 0 DISPLAY.DL_ 9-23-94 6:40a 91680 0 DSPRES.DL_ 9-26-94 9:44p 966 0 HD480AC.DSP 9-26-94 9:44p 960 0 HD480BC.DSP 9-26-94 9:44p 970 0 HD600BC.DSP 9-26-94 9:44p 1135 0 HD768BC.DSP 10-04-94 4:09p 26164 0 IBMVGA32.DL_ 9-01-94 7:52p 102 0 ISWINDOW.CO_ 10-10-94 10:22p 26593 0 P9000 9-26-94 9:45p 278 0 P9000A.DSP 9-26-94 9:45p 4335 0 P9000B.DSP 9-26-94 9:45p 31612 0 P9000M.DSP 10-10-94 10:22p 246058 0 P9000SYS 10-10-94 10:23p 25903 0 P9100 9-26-94 9:45p 48358 0 P9100M.DSP 10-10-94 10:23p 258828 0 P9100SYS 10-10-94 10:21p 198808 0 POWER_9K 9-26-94 9:44p 283 0 PSBGA32A.DSP 9-26-94 9:44p 1447 0 PSMONO.DSP 9-26-94 9:45p 792 0 PSS3A.DSP 9-26-94 9:44p 4878 0 PSSVGA32.DSP 9-26-94 9:44p 6345 0 PSVGA32.DSP 9-26-94 9:44p 12920 0 PSXGA32.DSP 9-26-94 9:45p 277 0 S3864A.DSP 10-08-94 8:14p 6551 0 SCREEN01.SY_ 10-08-94 8:14p 6496 0 SCREEN02.SY_ 9-26-94 9:44p 1030 0 SP480AC.DSP 9-26-94 9:44p 1028 0 SP480BC.DSP 9-26-94 9:45p 328 0 TLIW32A.DSP 9-26-94 9:44p 966 0 TR480AC.DSP 9-26-94 9:44p 963 0 TR480BC.DSP 9-26-94 9:44p 974 0 TR600BC.DSP 9-26-94 9:44p 1138 0 TR768BC.DSP 9-26-94 9:44p 963 0 TS480AC.DSP 9-26-94 9:44p 959 0 TS480BC.DSP 9-26-94 9:44p 969 0 TS600BC.DSP 9-26-94 9:44p 1135 0 TS768BC.DSP 12-07-93 1:00p 1994 0 VESA.EX_ 10-10-94 10:21p 118094 0 VGA 10-10-94 5:54p 70967 0 VSVGA.SY_ 10-10-94 5:56p 33571 0 VVGA.SY_ 9-26-94 9:45p 260 0 WD24_31A.DSP 9-26-94 9:44p 968 0 WD480AC.DSP 9-26-94 9:44p 963 0 WD480BC.DSP 9-26-94 9:44p 974 0 WD600BC.DSP 9-26-94 9:44p 1139 0 WD768BC.DSP 9-26-94 9:45p 277 0 WDC33A.DSP 10-02-94 7:55p 2762 0 WINVGA 10-10-94 10:22p 93533 0 WINXGA 10-10-94 10:21p 244636 0 XGA 66 file(s) 1800213 bytes used 0 bytes free WARP DISPLAY DISK_2 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-10-94 10:23p 70966 0 CGA 10-07-94 3:25p 154758 0 CIRRUS.DL_ 9-26-94 9:45p 15631 0 CL54XB.DSP 9-26-94 9:45p 708 0 CL54XM.DSP 10-10-94 10:26p 281419 0 CLWINDRV 10-10-94 10:23p 94373 0 EGA 9-26-94 9:44p 4482 0 PSBGA32B.DSP 9-26-94 9:44p 4307 0 PSCGA16.DSP 9-26-94 9:44p 4349 0 PSEGA16.DSP 8-18-94 7:41p 6825 0 SETMODE.EX_ 9-23-94 9:01p 57704 0 SV480256.DL_ 9-23-94 9:27p 57697 0 SV600256.DL_ 9-23-94 9:45p 58495 0 SV768256.DL_ 9-26-94 9:45p 4122 0 SVGA480A.DSP 9-26-94 9:45p 4122 0 SVGA480B.DSP 9-26-94 9:45p 4189 0 SVGA600B.DSP 9-26-94 9:45p 4183 0 SVGA768B.DSP 9-26-94 9:45p 13292 0 TLIW32B.DSP 9-26-94 9:45p 755 0 TLIW32M.DSP 9-29-94 12:57a 161544 0 TLIW32PM.DL_ 8-18-94 7:41p 6758 0 VMODE.CO_ 10-10-94 10:24p 38622 0 WIN8514 10-10-94 10:25p 281818 0 WINTLI32 9-15-94 11:48p 43446 0 WSPDBF.DR_ 9-15-94 11:51p 44173 0 WSPDSBF.DR_ 9-15-94 11:48p 43256 0 WSPDSF.DR_ 9-15-94 11:51p 43968 0 WSPDSSF.DR_ 29 file(s) 1505962 bytes used 0 bytes free WARP DISPLAY DISK_3 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 9-26-94 9:45p 15906 0 PSS3B.DSP 9-26-94 8:01p 157675 0 S3864 9-26-94 9:45p 13838 0 S3864B.DSP 9-26-94 9:45p 741 0 S3864M.DSP 10-05-94 12:29a 150086 0 S3VIDEO 10-10-94 10:27p 408503 0 S3WIN 10-10-94 10:29p 886527 0 WIN864 10-10-94 10:29p 199301 0 WIN86432 10 file(s) 1832577 bytes used 0 bytes free WARP DISPLAY DISK_4 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-12-94 11:43a 151342 0 ATIM32 9-26-94 9:45p 16913 0 ATIM32B.DSP 9-26-94 9:45p 699 0 ATIM32M.DSP 10-12-94 11:43a 152209 0 ATIM64 9-09-94 7:34p 1159 0 ATIM64.SY_ 9-26-94 9:45p 26663 0 ATIM64B.DSP 9-26-94 9:45p 699 0 ATIM64M.DSP 10-08-94 1:23a 4995 0 VAD32.SY_ 10-01-94 6:31a 3139 0 VAD64.SY_ 9-26-94 9:45p 9238 0 WD24B.DSP 9-26-94 9:45p 9241 0 WD24_31B.DSP 9-26-94 9:45p 736 0 WD24_31M.DSP 10-12-94 11:44a 176776 0 WD3116.DR_ 10-12-94 11:44a 134709 0 WD31_8.DR_ 10-12-94 11:45a 181391 0 WD3316.DR_ 10-12-94 11:44a 155660 0 WD33_8.DR_ 9-26-94 8:01p 147683 0 WD90C24.DL_ 9-26-94 8:01p 145124 0 WD90C33.DL_ 9-26-94 9:45p 10674 0 WDC33B.DSP 9-26-94 9:45p 737 0 WDC33M.DSP 10-12-94 11:45a 218624 0 WINM32 10-12-94 11:46a 126516 0 WINM64 24 file(s) 1674927 bytes used 0 bytes free PRINTER DRIVER DISK_1 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 10-12-94 11:36a 80696 0 EPSON.DR_ 10-12-94 11:36a 5991 0 EPSON.EA_ 10-12-94 11:37a 85252 0 HPDJPM.DR_ 10-12-94 11:37a 4915 0 HPDJPM.EA_ 10-12-94 11:37a 171135 0 IBM52XX.DR_ 10-12-94 11:37a 3695 0 IBM52XX.EA_ 10-12-94 10:57a 56716 0 IBMNULL.DR_ 10-12-94 11:35a 4565 0 IBMNULL.EA_ 10-12-94 11:38a 362616 0 IBMPCL5.DR_ 10-12-94 11:38a 4157 0 IBMPCL5.EA_ 10-12-94 11:36a 502262 0 LASERJET.DR_ 10-12-94 11:36a 5990 0 LASERJET.EA_ 10-12-94 11:37a 151330 0 PLOTTERS.DR_ 10-12-94 11:37a 4033 0 PLOTTERS.EA_ 10-12-94 11:37a 175 0 PMPLOT.EA_ 10-12-94 11:37a 61255 0 PMPLOT.QP_ 10-12-94 11:04a 28174 0 PRDESC.LST 10-10-94 5:03a 798 0 PRDRV.LST 10-12-94 11:36a 206185 0 PSCRIPT.DR_ 10-12-94 11:36a 9270 0 PSCRIPT.EA_ 22 file(s) 1749210 bytes used 0 bytes free PRINTER DRIVER DISK_2 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 3-11-94 4:37p 8558 0 40291730.WPD 3-11-94 4:37p 11028 0 40293930.WPD 7-28-94 1:51p 8675 0 4039PW31.WPD 3-11-94 4:37p 11304 0 4039W31.WPD 3-11-94 4:37p 6750 0 4079W31.WPD 7-25-94 3:39p 112816 0 FI4037.EXE 7-25-94 3:39p 14406 0 FI4037.HLP 3-11-94 4:37p 5715 0 IBM17521.WPD 3-11-94 4:37p 27184 0 IBM239X.DRV 3-11-94 4:37p 8185 0 IBM39521.WPD 3-11-94 4:37p 69152 0 IBM4019.DRV 10-10-94 10:17p 317763 0 IBM4019.DR_ 10-10-94 10:17p 3866 0 IBM4019.EA_ 3-11-94 4:37p 92864 0 IBM4029.DRV 7-25-94 3:39p 142048 0 IBM4037.DRV 7-25-94 3:39p 17263 0 IBM4037.HLP 7-25-94 3:39p 6910 0 IBM4037P.HLP 1-14-94 9:20a 11728 0 IBM4070.DRV 3-11-94 4:37p 93184 0 IBM40X9.DLL 10-10-94 10:17p 268316 0 IBM42XX.DR_ 10-10-94 10:17p 4064 0 IBM42XX.EA_ 10-07-94 9:33p 49934 0 IBM52012.DR_ 10-10-94 10:17p 4541 0 IBM52012.EA_ 10-10-94 10:18p 303222 0 IBMPCL3.DR_ 10-10-94 10:18p 3788 0 IBMPCL3.EA_ 10-10-94 10:18p 138046 0 OMNI.DR_ 10-10-94 10:18p 6377 0 OMNI.EA_ 1-14-94 9:20a 56784 0 SF4019.EXE 10-10-94 10:18p 38743 0 SMGXPJET.DR_ 10-10-94 10:18p 3711 0 SMGXPJET.EA_ 32 file(s) 1846925 bytes used 0 bytes free PRINTER DRIVER DISK_3 10-12-94 1:00p <DIR> 0 . 10-12-94 1:00p <DIR> 0 .. 3-11-94 4:37p 11856 0 IBM238X.DRV 1-14-94 9:20a 42928 0 IBM5183.DRV 7-25-94 3:39p 179856 0 IBMPCL5.DRV 3-11-94 4:37p 22918 0 IBMPCL5.HLP 7-25-94 3:39p 221217 0 IBMPCL5A.DRV 3-11-94 4:37p 12962 0 IBMPCL5O.HLP 9-19-94 9:44p 172160 0 IJ4076.DRV 3-11-94 4:37p 14231 0 IJ4076.HLP 3-11-94 4:37p 9668 0 IJ4076O.HLP 9-01-94 8:12p 200064 0 LEXF4047.DLL 9-01-94 8:12p 25207 0 LEXF4047.HLP 9-19-94 9:44p 212960 0 LEXF4076.DLL 3-11-94 4:37p 19151 0 LEXF4076.HLP 7-25-94 3:39p 211970 0 LEXFINST.DLL 3-11-94 4:37p 20066 0 LEXFINST.HLP 9-01-94 8:12p 15520 0 LEXMMGR.DLL 9-01-94 8:12p 19644 0 LEXMMGR.HLP 9-01-94 8:12p 202176 0 LM4047.DRV 9-01-94 8:12p 26207 0 LM4047.HLP 9-01-94 8:12p 15743 0 LM4047O.HLP 9-01-94 8:12p 14230 0 LM4076.HLP 7-25-94 3:39p 33693 0 LMPCL5A.HLP 7-25-94 3:39p 16046 0 LMPCL5AO.HLP 9-01-94 8:12p 114641 0 PTAPIW16.DLL 26 file(s) 1835114 bytes used 0 bytes free